Extending Anentropic’s answer: boot2docker is the old app for Mac and Windows, docker-machine is the new one. Firstly, list your machines: $ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM default * virtualbox Running tcp://192.168.99.100:2376 Then select one of the machines (the default one is called default) and: $ docker-machine ip default 192.168.99.100
Ok, I think I got it. The client is the docker command installed into OS X. The host is the Boot2Docker VM. The daemon is a background service running inside Boot2Docker. This variable tells the client how to connect to the daemon. When starting Boot2Docker, the terminal window that pops up already has DOCKER_HOST set, … Read more
It looks like you need to upgrade the VM after installing boot2docker: if you are upgrading from boot2docker 0.12 or later, you can update your existing virtual machine (after upgrading using the installer) using boot2docker stop && boot2docker download && boot2docker up – and you will not lose your existing data. (https://github.com/boot2docker/osx-installer/releases/tag/v1.1.0)
When you search for a docker image on Docker hub, there will be 2 tabs- Repo Info and Tags. Open Tags tab and you will see the sizes of all the types of images you can pull for that image.
You don’t need to run any docker commands as sudo when you’re using boot2docker as every command passed into the boot2docker VM runs as root by default. You’re seeing the error when you’re running as sudo because sudo doesn’t have the DOCKER_HOST env set, only your user does. You can confirm this by doing a: … Read more
I’ve decided to add my own answer with the best solution I’ve found so far. I’ll update this if I find better options. Best solution so far The best solution I’ve found for setting up a productive development environment with Docker on OS X is: Boot2Docker + Rsync. With rsync, build times in a Docker … Read more
Use COPY command like this: COPY foo.txt /data/foo.txt # where foo.txt is the relative path on host # and /data/foo.txt is the absolute path in the image read more details for COPY in the official documentation An alternative would be to use ADD but this is not the best practise if you dont want to … Read more
Containers can be built using build arguments (in Docker 1.9+) which work like environment variables. Here is the method: FROM php:7.0-fpm ARG APP_ENV=local ENV APP_ENV ${APP_ENV} RUN cd /usr/local/etc/php && ln -sf php.ini-${APP_ENV} php.ini and then build a production container: docker build –build-arg APP_ENV=prod . For your particular problem: FROM debian ENV http_proxy ${http_proxy} and … Read more
Yes, you can do this. What you are describing is a bind mount. See https://docs.docker.com/storage/bind-mounts/ for documentation on the subject. For example, if I want to mount a folder from my home directory into /mnt/mydata in a container, I can do: docker run -v /Users/andy/mydata:/mnt/mydata myimage Now, /mnt/mydata inside the container will have access to … Read more
Those documents are outdated. I’m guessing the 1.6 in the URL is for Docker 1.6, not Compose 1.6. Check out the correct syntax here: https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode. You are looking for network_mode when using the v2/v3 YAML format.