docker-devenv Need update to more recent dependencies?

The step of "./bin/devenv install" is failing part way through. It leaves the vagrantbox without a valid running docker process.

Looks like this might be a problem with recent Ubuntu package revisions:

Pulling repository relateiq/kafka
4e94ec485d59: Download complete
511136ea3c5a: Download complete
6170bb7b0ad1: Download complete
9cd978db300e: Download complete
5a17698d876e: Download complete
7184ebf797e3: Download complete
6603e71ac5b4: Download complete
73e854c96eb4: Download complete
6f59256fc631: Download complete
ee13cc9c0c22: Download complete
a902a0db5c2a: Download complete
3d12bc3bcfdf: Download complete
29c270c96e19: Download complete
961e22045b00: Download complete
d4b27420da40: Download complete
7f9cc2b409a6: Download complete
4938e6a6ef6f: Download complete
b7f1e7ef3c14: Download complete
Sending build context to Docker daemon 3.072 kB
Sending build context to Docker daemon
Step 0 : FROM ubuntu:12.04
 ---> b9e56c8f2cf5
Step 1 : ENV REFRESHED_AT 2013-11-16
 ---> Using cache
 ---> 4f21328ffdc0
Step 2 : RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list
 ---> Using cache
 ---> 0060e1b02a18
Step 3 : RUN apt-get update
 ---> Using cache
 ---> 73373cac48d3
Step 4 : RUN apt-get upgrade -y
 ---> Using cache
 ---> 05315689f6b8
Step 5 : run apt-get -y -q install aptitude sudo apt-utils ntp build-essential curl tzdata wget less dnsutils gzip netcat screen unzip sysstat git python-software-properties vim zsh
 ---> Running in 851609f9aabf
Reading package lists...
Building dependency tree...
Reading state information...
gzip is already the newest version.
tzdata is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 build-essential : Depends: libc6-dev but it is not going to be installed or
                            libc-dev
                   Depends: g++ (>= 4:4.4.3) but it is not going to be installed
                   Depends: dpkg-dev (>= 1.13.5) but it is not going to be installed
 git : Depends: perl-modules but it is not going to be installed
       Depends: liberror-perl but it is not going to be installed
 python-software-properties : Depends: python2.7 but it is not going to be installed
                              Depends: python (>= 2.7.1-0ubuntu2) but it is not going to be installed
                              Depends: python (< 2.8) but it is not going to be installed
                              Depends: python-apt (>= 0.6.20ubuntu16) but it is not going to be installed
                              Depends: lsb-release but it is not going to be installed
                              Depends: python-gnupginterface but it is not going to be installed
                              Depends: unattended-upgrades but it is not going to be installed
                              Depends: python-pycurl but it is not going to be installed
 vim : Depends: libpython2.7 (>= 2.7) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
2014/07/25 02:27:57 The command [/bin/sh -c apt-get -y -q install aptitude sudo apt-utils ntp build-essential curl tzdata wget less dnsutils gzip netcat screen unzip sysstat git python-software-properties vim zsh] returned a non-zero code: 100
Sending build context to Docker daemon  2.56 kB
Sending build context to Docker daemon
Step 0 : FROM internal_registry:5000/base
2014/07/25 02:27:57 Invalid Registry endpoint: Get http://internal_registry:5000/v1/_ping: dial tcp 127.0.0.1:5000: connection refused
Sending build context to Docker daemon  2.56 kB
Sending build context to Docker daemon
Step 0 : FROM internal_registry:5000/base:latest
2014/07/25 02:27:57 Invalid Registry endpoint: Get http://internal_registry:5000/v1/_ping: dial tcp 127.0.0.1:5000: connection refused
Sending build context to Docker daemon  2.56 kB
Sending build context to Docker daemon
Step 0 : FROM internal_registry:5000/oracle-java7
2014/07/25 02:27:57 Invalid Registry endpoint: Get http://internal_registry:5000/v1/_ping: dial tcp 127.0.0.1:5000: connection refused
Sending build context to Docker daemon 22.53 kB
Sending build context to Docker daemon
Step 0 : FROM internal_registry:5000/base:latest
2014/07/25 02:27:57 Invalid Registry endpoint: Get http://internal_registry:5000/v1/_ping: dial tcp 127.0.0.1:5000: connection refused
Sending build context to Docker daemon  2.56 kB
Sending build context to Docker daemon
Step 0 : FROM internal_registry:5000/oracle-java7
2014/07/25 02:27:57 Invalid Registry endpoint: Get http://internal_registry:5000/v1/_ping: dial tcp 127.0.0.1:5000: connection refused
Sending build context to Docker daemon  2.56 kB
Sending build context to Docker daemon
Step 0 : FROM internal_registry:5000/oracle-java7
2014/07/25 02:27:57 Invalid Registry endpoint: Get http://internal_registry:5000/v1/_ping: dial tcp 127.0.0.1:5000: connection refused
Connection to 127.0.0.1 closed.

Jul 25 '14 02:07 mtnygard

I think there's some confusion in the README for setup. I'm seeing a similar issue:

⇒ ./bin/devenv install Already up-to-date. Installing docker registry and images: /vagrant/bin/update.sh: line 3: docker: command not found /vagrant/bin/update.sh: line 4: docker: command not found /vagrant/bin/install.sh: line 12: docker: command not found /vagrant/bin/install.sh: line 12: docker: command not found /vagrant/bin/install.sh: line 17: docker: command not found Connection to 127.0.0.1 closed.

Looks like the initial setup of the Vagrant instance is missing a docker install. So it appears (at least with how I ran the initial setup that this bit got skipped: https://github.com/wsargent/docker-devenv/blob/master/Vagrantfile#L36-L66)

Going to start fresh and see if I can get the right setup :)

Aug 20 '14 18:08 atomantic

Here's the process that got me into that pickle:

git clone [email protected]:wsargent/docker-devenv.git # actually, I forked it, but same deal :) cd docker-devenv vagrant up vagrant reload ./bin/devenv install

Am I misreading the readme?

Aug 20 '14 18:08 atomantic

Aha! I had missed one thing. The first time I started vagrant up, I got a configuration block because I already had redis running on my host osx--so that killed the process but I think it left vagrant in a partially implemented state.

Handy note in case anyone gets an error like this from the vagrant up stage:

⇒  vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'docker-ubuntu-12.04.3-amd64-vbox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: docker-devenv_default_1408560615235_8365
==> default: Clearing any previously set forwarded ports...
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 8005 is already in use
on the host machine.

To fix this, modify your current projects Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 8005, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding.

run lsof -n -i4TCP:OFFENDINGPORT | grep LISTEN e.g. lsof -n -i4TCP:8005 | grep LISTEN

and kill -9 the pid or gracefully stop whatever is in the way, then vagrant reload

Aug 20 '14 18:08 atomantic