Official Docker image abandoned?

necmettin · July 8, 2026, 1:58pm

I see the latest Docker image is from 2021. Is it abandoned? Is everybody running Meteor in Galaxy or directly on their servers without Docker?

I see the geoffreybooth/meteor-base - Docker Image was updated only two months ago. It this the right way to go?

vooteles · July 8, 2026, 7:20pm

I am using that geoffreybooth image myself. I figure if it’s good enough for Disney it’s good enough for me too. And the maintainer’s track record of keeping up with Meteor updates has been solid to the best of my knowledge. You can see a lot of releases on Docker Hub.

Right now there’s a small issue with getting the image for 3.5 pushed to Docker Hub. There was a problem with getting 3.5 assets from meteor.com, which @italojs fixed very quickly. And then today a bug regarding versioning of npm lock files prevented the 3.5 from getting pushed. But here again @italojs took care of things and submitted a PR today in a matter of minutes after getting pinged. So really good work from the Meteor team. Hopefully the 3.5 image will be up soon.

A potential alternative image for Meteor builds might be zodern/meteor:

Have not used it for a while, but according to the docs it should work for version 3. If I recall correctly the builds should be larger with that image. But this is just from memory, not really sure if that’s correct.

vooteles · July 9, 2026, 6:56pm

Update: geoffreybooth/meteor-base:3.5 is now up at Docker Hub.

harry97 · July 10, 2026, 6:32am

italojs · July 13, 2026, 1:21pm

Today we arent mantaining any docker image, please, use the images from the community

harry97 · July 14, 2026, 8:15am

But doesn’t Galaxy/@philippeoliveira/@fredmaiaarantes maintain their own images that the community can use??

xet7 · September 17, 2026, 4:33pm

Meteor 3 WeKan FLOSS kanban has MIT license. These GitHub workflows build Meteor 3 WeKan to Docker and many other platforms. Anyone is welcome to use these for their Meteor 3 builds etc. These are maintained, with daily new releases of WeKan.

github.com/wekan/wekan

.github/workflows/release-all.yml

main

name: Release All Platforms

# Triggered manually via GitHub CLI or the Actions UI.
# Usage:
#   gh workflow run release-all.yml -f old_version=9.35 -f new_version=9.36
#
# Or use the convenience script (bumps versions, commits, pushes, then triggers):
#   ./releases/release-all.sh 9.35 9.36
#
# WeKan's default database is MongoDB, which ships server binaries only for amd64
# and arm64 (+ the win64/mac bundles). On every OTHER architecture that has a
# Node.js 24 build — ppc64le, s390x, riscv64 — there is no MongoDB, so those
# bundles ship FerretDB v1 instead: the wekan/FerretDB fork with its embedded
# pure-Go SQLite backend, which speaks the MongoDB wire protocol. FerretDB is
# built + released SEPARATELY (wekan/FerretDB, its own build.sh) as individual
# per-arch binaries; each bundle job downloads ONLY the ferretdb-<arch> binary for
# the platform it targets and bakes it in, so amd64/arm64 users can opt into it
# too (WEKAN_DB=ferretdb, `snap set wekan
# database=ferretdb`, or Docker env). Whichever backend is chosen binds the same
# MongoDB port, so MONGO_URL is unchanged. ppc64le/s390x/riscv64 are now covered

This file has been truncated. show original

Making a new release

git clone https://github.com/wekan/wekan

cd wekan

./releases/release-all.sh

github.com/wekan/wekan

releases/release-all.sh

main

#!/bin/bash
if [ -n "${ZSH_VERSION:-}" ]; then exec /bin/bash "$0" "$@"; fi

# WeKan REMOTE release script — pushes your CHANGELOG.md edit and triggers the
# GitHub Actions release workflow, which does EVERYTHING else remotely.
#
# For a fully LOCAL release (build on this machine), use ./releases/release.sh.
# This script (release-all.sh) is the REMOTE path: nothing is built, bumped or
# published on your machine — GitHub Actions does it all, in parallel.
#
# Usage:
#   1. Add your changes under a "# Upcoming WeKan ® release" section in
#      CHANGELOG.md - there isn't one lying around empty between releases,
#      so create it yourself from docs/DeveloperDocs/Changelog-Upcoming-Template.md
#      the moment you have a real entry for it.
#   2. Run (NO version number needed):
#        ./releases/release-all.sh
#      The script renames "# Upcoming ..." to the next version (always +1 minor)
#      dated today. You can still override explicitly:
#        ./releases/release-all.sh 9.35 9.36       # PREVIOUS NEW

This file has been truncated. show original

FerretDB v1 Fork by xet7 with telemetry removed, replacement for MongoDB 7 server

Node.js patches, for many additional CPU/OS

Mongo-tools-patches with telemetry removed, many additional OS/CPU

Mongosh-patches, with telemetry removed, many additional OS/CPU

jakabasej06 · September 20, 2026, 8:32am

Good point. For Meteor 3 compatibility, community templates that set NODE_ENV=production and use standard npm install --production inside the built bundle directory eliminate dependencies on deprecated framework base images.