Skip to content

Latest commit

 

History

History
75 lines (49 loc) · 3.44 KB

DockerOptions.md

File metadata and controls

75 lines (49 loc) · 3.44 KB

Docker on your system

If you want to run docker on your system, what's the best available option?

Linux Options

🐧 If you're running Linux, there isn't much more to do---you can simply install the docker-cli tool and take advantage of a few extra native options.

Mac Options

🍏 If you're running a Mac, whether Intel or M1/Arm64, using Docker Desktop for Mac will be your best option. You can take advantage of paravirtualization offered by Mac OS, meaning your docker environment will be relatively performant. You can also still use VirtualBox images.

Windows Options...

🪟 If you're Windows, you can run Docker, by there isn't a simple solution that let's you fully take advantage of everything you'd want to do.

  1. You can install Docker Desktop for Windows---however, you won't be able to easily run virtualization software, such as VirtualBox at the same time.

    In this scenario, you can toggle between using Docker or VirtualBox, by toggling whether you have a hypervisor running, and then rebooting each time you change it.

    bcdedit /set hypervisorlaunchtype auto
bcdedit /set hypervisorlaunchtype off

  2. Alternatively, you can try to use Hyper-V as a virtualization provider. The primary limitation of this approach is that not many linux distributions provide out of the box headless VM images that will work in Hyper-V. But if you did get it working, you can use Docker and Hyper-V at the same time.

  3. You can simply install the docker-cli tools and run the docker engine in a VM in VirtualBox. To use the docker-engine, you just need to set your environment variables to set the ip address of your VM.

    Prepare your docker vm

    bakerx run docker-vm focal --ip 192.168.99.101
bakerx stop docker-vm

# Map your project to your directories
vboxmanage sharedfolder add docker-vm --name "scripts" --hostpath C:/users/chris/classes/519/P-done/lib/scripts --automount
vboxmanage sharedfolder add docker-vm --name "downloads" --hostpath C:/users/chris/classes/519/P-done/tmp --automount

bakerx run docker-vm focal --ip 192.168.99.101
bakerx ssh docker-vm

# Get docker
curl -sSL https://get.docker.com/ | sh

# Add yourself to shared directories
vagrant@ubuntu-focal: sudo adduser $USER vboxsf

#Update the docker daemon to listen to outside connections:
vagrant@ubuntu-focal:/etc/systemd$ cat /lib/systemd/system/docker.service | grep dockerd
 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock -H tcp://0.0.0.0:2375
 
# Restart service 
# Reload the systemd daemon.
vagrant@ubuntu-focal:/etc/systemd$  sudo systemctl daemon-reload

# Restart Docker.
vagrant@ubuntu-focal:/etc/systemd$  sudo systemctl restart docker

# Check dockerd is running with additional host
vagrant@ubuntu-focal:/etc/systemd$ ps -aux | grep dockerd
 root       10440  0.8  6.9 1087792 69368 ?       Ssl  18:08   0:00 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock -H tcp://0.0.0.0:2375

    Install docker command line tools and point it to the docker engine running in your VM:

    choco install docker-cli -y
SETX DOCKER_HOST tcp://192.168.99.101:2375

docker run hello-world

    Using docker-machine
    You can also use the docker-machine tool to manage this process for you. See more here.