Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Dangling Containers and Images #627

Open
RollsChris opened this issue May 8, 2024 · 3 comments
Open

[BUG] Dangling Containers and Images #627

RollsChris opened this issue May 8, 2024 · 3 comments
Labels
bug triage Issues that need to be looked at

Comments

@RollsChris
Copy link

RollsChris commented May 8, 2024

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

@RollsChris RollsChris added bug triage Issues that need to be looked at labels May 8, 2024
@Janjanus
Copy link

I have the same issue when running iotedgedev solution build. Did you find any solutions in the mean time?

@RollsChris
Copy link
Author

RollsChris commented Jun 12, 2024 via email

@RollsChris
Copy link
Author

Any news on this... anyone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Issues that need to be looked at
Projects
None yet
Development

No branches or pull requests

2 participants