Docker: team up to create a reference docker image for meteor

Hello everyone

I’m using Meteor a lot and I need Docker images for my work now (I didn’t need them before last week).

Since I almost immediately ran into the recent issue with v1.4.1 (process must be run without root privileges) I decided to create my own Meteor Docker image to be sure it works as I want it to run. Here it is:

https://hub.docker.com/r/cluxter/meteor-install/

Right now it works nice with the latest version of Meteor. This is the only thing I was able to do so far because I just started using Docker 1 week ago and because I also have other things to do (I just did it last night).

Basically this Docker image is based on base/archlinux, it downloads the Meteor install script, installs it as root (as it is expected officially), then switches to a brand new “meteor” user and runs $ meteor --version to download the latest Meteor version. This is a basic (and quite big) image but it’s made the proper way.

Hence you can build a new Docker image for any of your Meteor application by simply creating a Dockerfile at the root of your Meteor app containing this code:

FROM cluxter/meteor-install

I will soon create 2 flavors of this image: 1 for development and 1 for production. Right now this image is suited for development because the current image is basically running the command $ meteor and nothing else, so the app will run on default port 3000 and doesn’t build the Node.js package (which is what should be done for production because it’s much faster).

I want to improve this based on all the issues you will report on GitHub. We can start using the list @lpgeiger just wrote. The first thing we should probably do is reducing the size of the current image as much as possible (since using no root is already done). The GitHub is here:

BTW a lot of people keep talking about and relying on @arunoda for updates but it seems it has been difficult for him to maintain all of the Meteor components he has worked on so far (which is totally normal considering how big this task is). For example the kadira:flow-router which is the router recommended in the Meteor documentation hasn’t been updated since April 2016. So I think it’s time to rely more on ourselves for everything that MDG hasn’t been able to develop yet. They are doing an awesome work but our needs are even faster than what they can deliver - so let’s fix everything we can.

2 Likes