You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have noticed that when we build our modules using: iotedgedev solution build
It creates multiple containers and images.
It will do this whenever there is a change to a stage in our Dockerfile which causes it to rebuild.
Building the Dockerfile for the module, on its own, does not give this behavior which points to this tool.
Expected behavior
I expect it to clean up all intermediate containers/ images that it creates. and dosent need for the final image.
Actual behavior
It looks like a container per stage in our file and 2 images labeled . one of them is over 1GB
Steps to Reproduce
Create a new Edge solution with a blank module.
Fix the broken tool by adding a Dockerfile and module.json to the module.
Build the solution.
You should now see some strange containers and a couple images with as the name
Environment
iotedgedev, version 3.3.7
Python 2.7.18
pip 22.3.1 from /usr/local/lib/python3.9/dist-packages/pip (python 3.9)
Development machine: WSL with the offical iotedgedev container image
IoT Edge device OS Version: using the simulator
The text was updated successfully, but these errors were encountered:
No not yet, and if you look you will see it eating your harddrive disk if your using wsl. I have found a way to revert that but still very annoying.
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Jan de Boer ***@***.***>
Sent: Wednesday, June 12, 2024 4:34:12 PM
To: Azure/iotedgedev ***@***.***>
Cc: Christopher Rollings ***@***.***>; Author ***@***.***>
Subject: Re: [Azure/iotedgedev] [BUG] Dangling Containers and Images (Issue #627)
I have the same issue when running iotedgedev solution build. Did you find any solutions in the mean time?
—
Reply to this email directly, view it on GitHub<#627 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABOHIGZTS4Z6TX5H3TTD67LZHBS7JAVCNFSM6AAAAABJGTXYQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGM2DAMZYGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Description
We have noticed that when we build our modules using:
iotedgedev solution build
It creates multiple containers and images.
It will do this whenever there is a change to a stage in our Dockerfile which causes it to rebuild.
Building the Dockerfile for the module, on its own, does not give this behavior which points to this tool.
Expected behavior
I expect it to clean up all intermediate containers/ images that it creates. and dosent need for the final image.
Actual behavior
It looks like a container per stage in our file and 2 images labeled . one of them is over 1GB
Steps to Reproduce
Create a new Edge solution with a blank module.
Fix the broken tool by adding a Dockerfile and module.json to the module.
Build the solution.
You should now see some strange containers and a couple images with as the name
Environment
iotedgedev, version 3.3.7
Python 2.7.18
pip 22.3.1 from /usr/local/lib/python3.9/dist-packages/pip (python 3.9)
Development machine: WSL with the offical iotedgedev container image
IoT Edge device OS Version: using the simulator
The text was updated successfully, but these errors were encountered: