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
When executing this code, an unusual behavior begins, first two images are created, one with the name Ubuntu and the other None, then containers are created up to a total of 21.
I leave the captures of how the final result looks.
And these are the two images created.
Docker version
Any idea what my mistake would be?
The text was updated successfully, but these errors were encountered:
Of course, what happens is that when you create an image using that dockerfile using the terminal, the corresponding image is created, including prove using the std:: process of rust and everything is ok, but when I do it using the lib, the behavior that it creates comes out two images and 21 containers which is not what I'm expecting, it should only create 1 single image without containers because I'm just building the image
Hey @orelvis15 this is not an issue related to bollard. Container image are created using container. You have one container running for each command you set in your dockerfile. by default when you build using the docker cli it will remove them, when you use the API dirrectly you have to specify an option to delete them.
Look there https://docs.docker.com/engine/api/v1.41/#tag/Image/operation/ImageBuild
You will notice 2 options:
rm Remove intermediate containers after a successful build.
forcerm Always remove intermediate containers, even upon failure.
Hello Goodnight!.
I am testing an example of the slightly modified lib it would be running like this.
Dockerfile
When executing this code, an unusual behavior begins, first two images are created, one with the name Ubuntu and the other None, then containers are created up to a total of 21.
I leave the captures of how the final result looks.
And these are the two images created.
Docker version
Any idea what my mistake would be?
The text was updated successfully, but these errors were encountered: