Azure / Azure/iotedgedev

[BUG] Dangling Containers and Images

Open
#627 3 comments 0 reactions 0 assignees View on GitHub
bug triage
Dominant language
Python
Stars
166
Forks
76
PR merge metrics
No merged PRs in 30d

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.