HUB
Sign inSign up
meteor-alpine logo

staeke/meteor-alpine

By staeke

•Updated almost 7 years ago

Run meteor commands (like build) on Alpine Linux. It includes the meteor tool, but not much else.

Image
1

2.2K

staeke/meteor-alpine repository overview

Github: https://github.com/staeke/meteor-alpine⁠

If I'm late with a version, let me know with a Github issue and I'll publish a new version.

Available tags (i.e. Meteor versions): 1.8.2, 1.8.1, 1.8.0.2, 1.8.0.1, 1.8, 1.7.0.5, 1.7.0.4, 1.7.0.3, 1.7.0.2, 1.7.0.1, 1.7, 1.6.1.1, 1.6.1, 1.6.0.1

These are images to run the meteor tool on Alpine Linux. There are corresponding "runners" - much smaller - available at https://hub.docker.com/r/staeke/meteor-node-alpine/⁠. The idea is to use this image for building, and the "runner" image for running your production app. This image has had meteor installed with some fixes to make it functional on non-glibc system (i.e Alpine Linux). The node versions are always matched to the ones used by meteor for that meteor version. The image is built off node:XXX-alpine.

They are tagged with the specific meteor version, so for instance, for Meteor 1.8.2 you can write your Dockerfile as

FROM staeke/meteor-alpine:1.8.2
...

...or if you use npm

package.json:

"scripts": {
  "build": "docker build . --build-arg METEOR_VERSION=$(cat app/.meteor/release) -t my-app"
}

Dockerfile:

ARG METEOR_VERSION
FROM staeke/meteor-alpine:$METEOR_VERSION
...

⁠Details

⁠apk packages on the image

As bash is needed for a lot of meteor commands, that apk package is left on the image. No other packages are, so for instance if you want to run meteor create, you need to install git (RUN apk add --update git)

⁠A note on security and users

  • Meteor itself is installed for the user meteor (uid: 1001), but the docker command USER meteor is not yet issued, as you might want to add apk packages as root (or run all as root). But all you need to do otherwise is adding a USER meteor in your Dockerfile.
  • You can run all commands using root, as the environment is prepared (for instance METEOR_ALLOW_SUPERUSER is set to 1). I get it, there's a tradeoff between convenience and security. Common recommendations are to run containers as specific users. However, doing that will make volume sharing harder (you need to setup permissions) and copying a little more verbose (see below). On the other hand, you won't get warnings when running meteor.
  • Remember that if you set up your docker build using the meteor user, that you most typically want to run docker COPY commands with --chown=meteor flag.

Tag summary

Content type

Image

Digest

Size

208.4 MB

Last updated

almost 7 years ago

docker pull staeke/meteor-alpine:1.8.2