is your image building correctly? the name does not get set when there is an error in the build. This because every step in the build is a new image created and with an error you won’t get to the last step with the correctly named image btw you can set it manually with the … Read more
I was able to run a local image by setting the imagePullPolicy to Never. For example: apiVersion: v1 kind: Pod metadata: name: local-image-test spec: containers: – name: local-image-container image: local-image:latest imagePullPolicy: Never (Credit to https://github.com/kubernetes/kubernetes/issues/1293#issuecomment-357326426 for this solution)
Today I had the same issue that all containers are started when I boot my dev laptop, as restart: always was set in the .yml files. As I don’t want to touch the .yml files, I just found out (thx Bobby) how to alter this setting by: docker update –restart=no <MY-CONTAINER-ID>
Update 2019-01-31, thanks to ru10’s update, now there is a better way: screen ~/Library/Containers/com.docker.docker/Data/vms/0/tty Original Answer: After a while, I found following way to get a shell of the VM that was created by HyperKit: Run from terminal: screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty You will see an empty screen, then type enter, you will get a login prompt. … Read more
Specifically for Docker for Mac, because it’s a “GUI” app, there’s a workaround: osascript -e ‘quit app “Docker”‘ Since you’d want to restart, here’s the way to open it from the command line: open -a Docker There’s probably a more symmetrical command to open using osascript, but the open command seems more common than the … Read more
As @GabLeRoux has shared in a comment, the “Real Memory” usage is much lower than what you see in the “Memory” column in Activity Monitor. This document thoroughly explains memory usage on Mac OS with Docker Desktop and information is excerpted from there. To see the “Real Memory” used by Docker, right-click the column names … Read more
If you don’t want to map ports from your host to the container you can access directly to the docker range ip for the container. This range is by default only accessed from your host. You can check your container network data doing: docker inspect <containerNameOrId> Probably is better to filter: docker inspect <containerNameOrId> | … Read more
Docker for Mac volume mounts behave differently than the base Docker system. This is mostly because Docker tries to comply with Apple’s filesystem sandbox guidelines. As shown in Docker’s preferences, only certain paths are exported by macOS. /Users /Volumes /tmp /private /var in macOS is a symbolic link into /private. That is also true for … Read more
As mentioned in the above answers, you will find it in: screen ~/Library/Containers/com.docker.docker/Data/vms/0/tty Once you get the tty running you can navigate to /var/lib/docker
Depends what you’re trying to do. If you’re running with –net=host, localhost should work fine. If you’re using default networking, use the static IP 172.17.0.1. I suspect neither will behave quite the same as those domains.