Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker, Vagrant and VMWare Fusion

woss.name

Post reply on HN
Print view View original

1–10 of 12 posts

Re: Docker, Vagrant and VMWare Fusion

#3

Post by pmoriarty »

Can anyone shed some light on what the following does and why it's necessary?

   sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
"All we’re doing is installing the latest stable version of Docker, direct from Docker’s own apt repository, configuring it to listen for both TCP and socket connections, updating the rest of the system, and installing avahi for multicast DNS resolution."

Installing avahi for multicast DNS resolution? Why does he need avahi? Why does he need multicast DNS resolution?

[Update: I don't know why the person that replied deleted their comment, because it was useful info. Here it is, for posterity:

1) Add's the docker key from the Ubuntu keyserver, which is already trusted, so the docker packages can be installed.

2) Avahi lets him name his docker containers and then discover them on the local mac os host and the linux VM, eg wossname.nginx, rather than some dynamically assigned IP.]

Re: Docker, Vagrant and VMWare Fusion

#4

Post by [deleted] »

pmoriarty wrote: post #3

Can anyone shed some light on what the following does and why it's necessary? sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9 "All we’re doing is installing the latest stable version of Docker, direct from Docker’s own apt repository, configuring it to listen for both TCP and socket connections, updating the rest of the system, and installing avahi for m…

[deleted]

Re: Docker, Vagrant and VMWare Fusion

#5

Post by maspwr »

As mentioned in the article, Vagrant actually comes with built-in support [1] to run Docker containers. Ideally it would obviate the need to do some of the manual work done here to get this type of environment up and running.

  The Vagrant support for Docker uses boot2docker, which only supports VirtualBox, so I’m left high and dry.
You can use a proxy Vagrantfile to configure the type of machine that is used as the Docker host [2]. Unfortunately there is a bug [3] that make this not quite usable yet.

1. https://docs.vagrantup.com/v2/docker/index.html

2. https://github.com/maspwr/vagrant-docker-dev

3. https://github.com/mitchellh/vagrant/issues/4856

Re: Docker, Vagrant and VMWare Fusion

#6

Post by pmoriarty »

[deleted] wrote: post #4
pmoriarty wrote: post #3

Can anyone shed some light on what the following does and why it's necessary? sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9 "All we’re doing is installing the latest stable version of Docker, direct from Docker’s own apt repository, configuring it to listen for both TCP and socket connections, updating the rest of the system, and installing avahi for m…

[deleted]

Wouldn't it be simpler to just assign the docker instances a static IP and make a corresponding /etc/hosts entry?

Re: Docker, Vagrant and VMWare Fusion

#8

Post by vubuntu »

coherentpony wrote: post #2

Good lord, what a mess. How did it get this complicated?

It is messy because VM layer is unnecessary. If OSX had native support for containers or if ur dev laptop was linux then all you had to do was use docker directly with dockerfile. That is the purpose of docker. To make usage of container virtualization easy and standardized and to be used directly on baremetal. All the convolutions introduced by the VM virtualization will evaporate as container support becomes standard across all OS.

Re: Docker, Vagrant and VMWare Fusion

#9

Post by curun1r »

coherentpony wrote: post #2

Good lord, what a mess. How did it get this complicated?

The whole article can be boiled down to:

"The trouble is that I’m obstinate: I’ve paid for a VMWare Fusion license, and I’m insisting on using it."

VirtualBox is free, and all the work to make Docker run easily has already been done. But the author only wants to use VMWare, so it got complicated.

Re: Docker, Vagrant and VMWare Fusion

#10

Post by vubuntu »

vubuntu wrote: post #8
coherentpony wrote: post #2

Good lord, what a mess. How did it get this complicated?

It is messy because VM layer is unnecessary. If OSX had native support for containers or if ur dev laptop was linux then all you had to do was use docker directly with dockerfile. That is the purpose of docker. To make usage of container virtualization easy and standardized and to be used directly on baremetal. All the convolutions introduced by the VM virtualization will evaporate as container support becomes standa…

I am not vagrant user... but what role can it play when my dev laptop is ubuntu for eg? Does it become redundant layer if all my virtualization,configuration and deployment needs are met by docker and dockerfile?
Post reply on HN