When I wanted to inspect Docker-Container that existed in a remote Docker-registry, I normally used skopeo:
skopeo inspect docker://ubuntu:latest
{
"Name": "docker.io/library/ubuntu",
"Digest": "sha256:9a0bdde4188b896a372804be2384015e90e3f84906b750c1a53539b585fbbe7f",
"RepoTags": [
"10.04",
"12.04",
"12.04.5",
}
This command show me all the information about the image that I needed …
more ...In a .gitlab-ci.yml
job, if you do not specify a tag for an image, the latest
tag is used by default.
The default configuration of the gitlab-runner to pull Docker images is if-not-present
, which means the image is only loaded if it is not already present. This in turn …
Randomly some Docker-containers on a clients Linux machine wouldn’t start - they’d fail with the error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"EOF\"": unknown.
It didn’t matter …
more ...Often times I find a interesting or useful project on Github that is abandoned and has some issues. Then I hope that someone already forked the repository and continued working on it. To find a fresh fork, I had to go to the Insights-tab in the repository, click on “Forks …
more ...