Docker: Reverse Engineering of an Image
You can check how an image was created using docker history <image-name> –no-trunc Update: Check dive which is a very nice tool that allows you to views image layers.
docker-image
Running a Docker file stored locally
The process to run Dockerfile is: docker build . -t [tag] -f /path/to/Dockerfile And then: docker run -d tag
Docker Build throwing a error -“Docker output clipped, log limit 1MiB reached”
Per https://docs.docker.com/config/containers/logging/configure/ it suggests to: Restart Docker for the changes to take effect for newly created containers. Existing containers do not use the new logging configuration. Unfortunatelly docker build doesn’t support –log-opt max-buffer-size=XXXm, but buildx does As “the last shoot”, you can remove –progress plain if you don’t acutally need it
Docker save/load lose original image repository/name/tag
Use docker save -o filename.tar <repo>:<tag> The command docker save <image id> removes the repository and tag names. To solve this, use docker save <repo>:<tag> it will keep the repository and tag name in the saved file. For example: docker save -o ubutu-18.04.tar ubuntu:18.04
SSH agent forwarding during docker build
For Docker 18.09 and newer You can use new features of Docker to forward your existing SSH agent connection or a key to the builder. This enables for example to clone your private repositories during build. Steps: First set environment variable to use new BuildKit export DOCKER_BUILDKIT=1 Then create Dockerfile with new (experimental) syntax: # … Read more
Docker image layer: What does `ADD file: in /` mean?
That Docker Hub history view doesn’t show the actual Dockerfile; instead, it shows content essentially extracted from the docker history of the image. That doesn’t preserve the specific details you’re looking for: it doesn’t remember the names of base images, or the build-context file names of things that get ADDed or COPYed in. Chasing through … Read more
Error: “Failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest” when building a Docker image
The cause was simple. I had my Docker desktop running on Linux containers and the image was build from a Windows image. Simply switching to Windows containers solved the problem. The message is clueless, so I hope this save some time for others.
Docker – What is proper way to rebuild and push updated image to docker cloud?
I found the problem, thanks to @lorenzvth7! I’ve had two images with same tag (which i was pushing to cloud). Solution is: Inspect your images and find two or more with the same tag: docker images Delete them: docker rmi –force ‘image id’ Thats it! Follow steps from my question above.
Cannot remove images even though no container is running
You cannot remove images having multiple repositories without the force modifier, see Docker docs for more info. docker images REPOSITORY TAG IMAGE ID CREATED SIZE repository/image-name tag a8e6fa672e89 10 days ago 344MB repository2/image-name tag a8e6fa672e89 10 days ago 344MB If you want to do it manually, instead of using the image id to remove the … Read more