Proposal: standardizing the names of the Plone container image repositories

Announcements
,
1

We plan to rename the GitHub repositories that host Plone's container images so they follow a single container-* convention. Only the repositories change — the image names on Docker Hub and GHCR stay exactly as they are.

Current repository New name
plone/plone-backend plone/container-backend
plone/plone-frontend plone/container-frontend
plone/plone-zeo plone/container-zeo
plone/plone.docker plone/container-legacy

We will also create a new repository, plone/container-aurora, to be the home of the images for Aurora, the future React frontend of Plone.

Why: today the naming is inconsistent (plone-*, plone.docker) and it is not obvious from the name that a repository is about container images. A shared prefix makes them easy to find and gives Aurora a natural place to land.

What this means for you:

  • docker pull plone/plone-backend:6.1 and friends keep working — nothing changes for image users.
  • GitHub redirects the old repository URLs, so existing clones and links keep working. Still, update your remotes when convenient.
  • Issues, PRs, and CI history move with the repositories.

Feedback welcome, especially if you see a reason not to do this, or have a better name for any of them (container-legacy is the one we are least sure about). If there are no objections, we will do the rename on 2026-09-10].

5 Likes
Plone Archeology: running Plone 1.0 to 4.2 in containers
2

Thanks! Small details and consistency matters on the long term :smiley:

As you are unsure about the legacy one: historical?

3

Seems like a good name, so `containers-historical` it is :slight_smile:

Current repository New name
plone/plone-backend plone/container-backend
plone/plone-frontend plone/container-frontend
plone/plone-zeo plone/container-zeo
plone/plone.docker plone/container-historical
4

The renaming is done. The Plone container image repositories on GitHub now share the container- prefix:

Before Now
plone/plone-backend plone/container-backend
plone/plone-frontend plone/container-frontend
plone/plone-zeo plone/container-zeo
plone/plone.docker plone/container-historical
— plone/container-aurora (already uses the new name)

Container image names do not change. You still pull plone/plone-backend, plone/plone-frontend, plone/plone-zeo and plone/plone exactly as before.

GitHub redirects the old repository URLs, so existing links and clones keep working. Still, please update your local clones.

Updating a local clone

Inside your clone, point origin to the new name (this example uses container-backend):

# SSH
git remote set-url origin git@github.com:plone/container-backend.git

# or HTTPS
git remote set-url origin https://github.com/plone/container-backend.git

# check
git remote -v
git fetch origin

The local folder keeps its old name. Rename it too if you like, e.g. mv plone-backend container-backend.

1 Like