Tyler Cipriani: Development Environments with Vagrant, Docker, and Supervisord

comment 1

2018-06-13T19:34:11Z

Such a great article, and a great insight. This pushed me into downloading docker and vagrant although I keep on getting the error “The Docker provider was able to bring up the host VM successfully but the host VM is still reporting that SSH is unavailable.”; been pulling my hair out for days…..

comment 2

2018-06-13T19:34:11Z

I wonder if you need to setup openssh via the dockerfile and run it as part of supervisord…?

comment 3

2018-06-13T19:34:11Z

any tips on where i’d start with that??

comment 4

2018-06-13T19:34:11Z

I tried to implement the code posted and, for some bizarre reason, nothing shows up on the browser when I go to http://localhost:8080/index.php. Looks like the ngnix is not forwarding the requests to PHP. Do you have a repo or something with the code so that I can test against your code? Thanks.

comment 5

2018-06-13T19:34:11Z

Sure: https://github.com/thcipriani/…

comment 6

2018-06-13T19:34:11Z

Unfortunately, the Vagrant support for Docker as a provider isn’t quite seamless across platforms as the documentation seems to indicate. Ports are not forwarded from the docker host vm to the main host machine automatically. The fix is to use a proxy Vagrantfile that explicitly forwards the ports you need. See https://gist.github.com/audion… for a discussion of the issue and https://github.com/simono/vm-e… for a simple and lightweight proxy Vagrantfile.

comment 7

2018-06-13T19:34:11Z

Unfortunately, it seems that as of Vagrant 1.6, the Vagrant support for Docker as a provider isn’t quite seamless across platforms as the documentation seems to indicate. Ports are not forwarded from the docker host vm to the main host machine automatically. The fix is to use a proxy Vagrantfile that explicitly forwards the ports you need. See https://gist.github.com/audion… for a discussion of the issue and https://github.com/simono/vm-e… for a simple and lightweight proxy Vagrantfile.

comment 8

2018-06-13T19:34:11Z

Extremely helpful. Thanks!

comment 9

2018-06-13T19:34:11Z

lo-and-below: love your wit. Wish I could get my stinkin’ Mac OS X > Vagrant > Docker > container > –volumes-from > chown > permissions > problems working, but I’ll be watching your blog, if only for the English prose. Keep it up!

comment 10

2018-06-13T19:34:11Z

Your position (state?) and process beautifully explained, thank you. Also a really well presented website.

comment 11

2018-06-13T19:34:11Z

Great article Tyler, and extremely well written. I’m setting up a continuous development environment for a personal Microsoft C# project and understanding how Docker/Chef/Vagrant intersect is surprisingly hard to do

comment 12

2018-06-13T19:34:11Z

I’m hoping to fix those issues too!

comment 13

2018-06-13T19:34:11Z

THANKS for sharing your project folder structure man! That’s the first post i found showing that stuff. I’ll definitely use this structure for learning about docker. Thanks again

Suggestion: As a OSX user i don’t have docker on my machine. Why not add “d.image =”ubuntu/latest" in the vagrant file instead of using this command before do a vagrant up ?

comment 14

2018-06-13T19:34:11Z

This is a great run down of using docker for local development. I’m working through a similar issue, but I’m setting up a LAMP stack. In your situation everything exists only in the container environment, except with /var/www linked to the host, with some help from vagrant. In your example however you’re not using a database, I was wondering how you would plan on persisting a database to the host file system. Taking a guess, would you just throw it somewhere with another VOLUME command in your Dockerfile, and sync it to a db folder?

As a side-note I’m considering using baseimage-docker as an image starting point as it solves a few different issues in the multi-process setup. It also uses runit which the author finds to provide better performance than supervisor, but I haven’t tested this.

Instead of using vagrant, in a docker-only situation the “sync folders” that vagrant is doing would have to be done via a docker run -v. How a container links to its host is host-dependent, and should be managed via each person rather than making assumptions about the host’s filesystem. This is one thing that your Vagrantfile sets up, although I suppose you could throw the docker -run... in a [docker-run.sh](http://docker-run.sh).

Thanks for writing up this, it solves my ninety percent of my use-case.

comment 15

2018-06-13T19:34:11Z

INFO interface: error: There was an error loading a Vagrantfile. The file being loaded

and the error message are shown below. This is usually caused by

a syntax error.

Path:

Line number: 6

Message: NoMethodError: undefined method `<<’ for #

There was an error loading a Vagrantfile. The file being loaded

and the error message are shown below. This is usually caused by

a syntax error.

Path:

Line number: 6

Message: NoMethodError: undefined method `<<’ for #

INFO interface: Machine: error-exit [“Vagrant::Errors::VagrantfileLoadError”, “There was an error loading a Vagrantfile. The file being loadedthe error message are shown below. This is usually caused bysyntax error.: number: 6: NoMethodError: undefined method `<<’ for #”]

comment 16

2018-06-13T19:34:11Z

I’m unclear if you’re telling me something is wrong in my post, or if you’re asking for help. Also, in future, use of a pastebin would be appreciated.

It is difficult to troubleshoot without knowing the contents of the Vagrantfile and os/version of host; however, what is clear is that whatever you’re sending the << message to is an object that doesn’t respond to that method. In my example above, d.ports is an Array that does accept the << message.

It’s entirely possible something about Vagrantfiles has changed in the almost exactly 2 years since this post.