conductoross/conductor-standalone is deprecated — use conductoross/conductor instead

[nthmost-orkes]

conductoross/conductor-standalone is deprecated — use conductoross/conductor instead

TL;DR: Replace conductoross/conductor-standalone with conductoross/conductor:latest.

The conductoross/conductor-standalone Docker Hub image is deprecated. It has not been updated since December 2023 (pinned at Conductor 3.15.0) while the project has continued releasing on conductoross/conductor (currently 3.22.3+). On 2026-06-30, the :latest tag on conductor-standalone will be replaced with a notice payload that prints a deprecation message and exits. Pinned tags (:3.15.0, etc.) remain available but unmaintained.

Replacement command

docker run -p 8080:8080 conductoross/conductor:latest

This is the working one-liner verified against the current image (see conductor-oss/conductor#1043, which fixed startup so SQLite is used by default with no external dependencies).

For a full local stack with the UI, use the Docker Compose file from the main repo:

git clone https://github.com/conductor-oss/conductor.git
cd conductor/docker
docker compose up

Migration FAQ

Why was conductor-standalone deprecated?
It fell out of sync with the release cadence (last published December 2023, Conductor 3.15.0). The main conductoross/conductor image now supports SQLite out of the box, making a separate standalone image unnecessary.

My docker-compose.yml references conductor-standalone. What do I change?
Replace the image name with conductoross/conductor:latest. No other changes are required for the basic single-container case.

I'm pinned to conductor-standalone:3.15.0. What happens after 2026-06-30?
Pinned tags remain available on Docker Hub but will not receive updates. You can continue using them, but you'll be running a 3-year-old server with no security fixes. We strongly recommend migrating before the sunset date.

What changes on 2026-06-30?
Only the :latest tag on conductor-standalone is overwritten — with an Alpine-based image that prints a deprecation notice and exits with code 1. This is intentional: it surfaces the migration to anyone still pulling :latest in a CI pipeline without breaking pinned references on the wider internet (blog posts, Stack Overflow answers, old tutorials).

Where do I report issues with the new image?
conductor-oss/conductor/issues

Tag lifecycle

When	conductor-standalone:latest	Pinned tags (:3.15.0, etc.)
Before 2026-06-30	Conductor 3.15.0 (Dec 2023 build)	Unchanged
After 2026-06-30	Notice payload — prints message, exits 1	Unchanged

Links

• conductoross/conductor on Docker Hub
• Getting started guide
• Tracking issue
• conductor-oss/conductor#1043 — the fix that makes this migration viable