Unable to run `shuttle run` due to `thread 'tokio-runtime-worker' panicked at /home/circleci/project/cargo-shuttle/src/provisioner_server.rs:261:18: failed to create exec to check if container is ready`

[jymchng]

What happened?

This is the logs:

Warning: shuttle-runtime 0.56.0 and Shuttle CLI 0.57.3 are incompatible.
Hint: A newer version of shuttle-runtime is available.
      Change its version to 0.57.3 in Cargo.toml to update it,
      or run this command: cargo add shuttle-runtime@0.57.3

    Starting shortener-asyncmove on http://127.0.0.1:8000

2025-11-14T17:17:30.485+01:00 [app] shuttle-runtime 0.56.0 starting: project-name 0.1.0
2025-11-14T17:17:30.487+01:00 [app]  WARN shuttle_runtime::start: Default tracing subscriber initialized (https://docs.shuttle.dev/docs/logs)
2025-11-14T17:17:30.487+01:00 [app]  INFO shuttle_runtime::rt: Loading resources
These secrets can be accessed by local service
┌────────────────────┐
│ Key                │
╞════════════════════╡
│ ADMIN_KEY          │
│ SERVER_PRIVATE_KEY │
└────────────────────┘

2025-11-14T17:17:30.494+01:00 [app]  INFO shuttle_runtime::rt: Provisioning DatabaseSharedPostgres

thread 'tokio-runtime-worker' panicked at /home/circleci/project/cargo-shuttle/src/provisioner_server.rs:261:18:
failed to create exec to check if container is ready: DockerResponseServerError { status_code: 409, message: "container 8c60d3395955bdabdd58065d04be5123b08c2181cb8486909d49800acad1881d is not running" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-11-14T17:17:37.503+01:00 [app] ERROR: Runtime Provisioning phase failed: error sending request for url (http://127.0.0.1:15848/projects/proj_LOCAL/resources)
Error: Runtime process exited with code 131

Version

v0.57.3

Which operating system(s) are you seeing the problem on?

Linux

Which CPU architectures are you seeing the problem on?

x86_64

Relevant log output

Warning: shuttle-runtime 0.56.0 and Shuttle CLI 0.57.3 are incompatible.
Hint: A newer version of shuttle-runtime is available.
      Change its version to 0.57.3 in Cargo.toml to update it,
      or run this command: cargo add shuttle-runtime@0.57.3

    Starting shortener-asyncmove on http://127.0.0.1:8000

2025-11-14T17:17:30.485+01:00 [app] shuttle-runtime 0.56.0 starting: project-name 0.1.0
2025-11-14T17:17:30.487+01:00 [app]  WARN shuttle_runtime::start: Default tracing subscriber initialized (https://docs.shuttle.dev/docs/logs)
2025-11-14T17:17:30.487+01:00 [app]  INFO shuttle_runtime::rt: Loading resources
These secrets can be accessed by local service
┌────────────────────┐
│ Key                │
╞════════════════════╡
│ ADMIN_KEY          │
│ SERVER_PRIVATE_KEY │
└────────────────────┘

2025-11-14T17:17:30.494+01:00 [app]  INFO shuttle_runtime::rt: Provisioning DatabaseSharedPostgres

thread 'tokio-runtime-worker' panicked at /home/circleci/project/cargo-shuttle/src/provisioner_server.rs:261:18:
failed to create exec to check if container is ready: DockerResponseServerError { status_code: 409, message: "container 8c60d3395955bdabdd58065d04be5123b08c2181cb8486909d49800acad1881d is not running" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-11-14T17:17:37.503+01:00 [app] ERROR: Runtime Provisioning phase failed: error sending request for url (http://127.0.0.1:15848/projects/proj_LOCAL/resources)
Error: Runtime process exited with code 131

Duplicate declaration

• I have searched the issues and there are none like this.

[jymchng]

Added logs from running shuttle run --debug.

# shuttle run --debug
2025-11-14T16:18:22.398562Z TRACE cargo_shuttle::config: looking for Shuttle.toml in /root/rust_project/project-name
2025-11-14T16:18:22.399152Z TRACE cargo_shuttle::config: no local Shuttle.toml found
2025-11-14T16:18:22.399320Z TRACE cargo_shuttle::config: using crate name as project name
2025-11-14T16:18:25.180982Z TRACE cargo_shuttle: starting a local run with args: RunArgs { port: 8000, external: false, raw: false, secret_args: SecretsArgs { secrets: None }, build_args: BuildArgsShared { release: false, bacon: false, docker: false, tag: None } }
2025-11-14T16:18:25.181112Z TRACE cargo_shuttle: Loading secrets from /root/rust_project/project-name/Secrets.toml
2025-11-14T16:18:25.181320Z TRACE cargo_shuttle: Loaded secrets keys=["SERVER_PRIVATE_KEY", "ADMIN_KEY"]
    Building /root/rust_project/project-name
2025-11-14T16:18:26.805973Z TRACE cargo_shuttle::builder: Finding Shuttle-related packages
2025-11-14T16:18:26.808212Z TRACE cargo_shuttle::builder: Found project-name
2025-11-14T16:18:26.808627Z DEBUG cargo_shuttle::builder: Gathered build args: BuildArgsRust { shuttle_runtime_version: Some("0.56.0"), cargo_chef: true, cargo_build: true, package_name: Some("project-name"), binary_name: Some("project-name"), features: None, no_default_features: false, mold: false }
    Blocking waiting for file lock on build directory
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 12s
2025-11-14T16:21:41.685622Z TRACE cargo_shuttle::builder: package compiled
2025-11-14T16:21:41.686319Z TRACE cargo_shuttle: runtime executable path="/root/rust_project/project-name/target/debug/project-name"
2025-11-14T16:21:41.686426Z DEBUG cargo_shuttle::util: Checking version of runtime binary at /root/rust_project/project-name/target/debug/project-name
2025-11-14T16:21:41.900202Z  WARN cargo_shuttle::util: shuttle-runtime and Shuttle CLI have incompatible versions
Warning: shuttle-runtime 0.56.0 and Shuttle CLI 0.57.3 are incompatible.
Hint: A newer version of shuttle-runtime is available.
      Change its version to 0.57.3 in Cargo.toml to update it,
      or run this command: cargo add shuttle-runtime@0.57.3

    Starting project-name on http://127.0.0.1:8000

2025-11-14T16:21:41.902025Z  INFO cargo_shuttle: Spawning runtime process path=/root/rust_project/project-name/target/debug/project-name
2025-11-14T17:21:41.987+01:00 [app] shuttle-runtime 0.56.0 starting: shortener_asyncmove 0.1.0
2025-11-14T17:21:41.989+01:00 [app]  WARN shuttle_runtime::start: Default tracing subscriber initialized (https://docs.shuttle.dev/docs/logs)
2025-11-14T17:21:41.989+01:00 [app] DEBUG shuttle_runtime::rt: Parsing environment variables
2025-11-14T17:21:41.992+01:00 [app] TRACE shuttle_runtime::rt: Starting health check server on port 20832
2025-11-14T17:21:41.993+01:00 [app]  INFO shuttle_runtime::rt: Loading resources
2025-11-14T17:21:41.993+01:00 [app] TRACE shuttle_runtime::rt: Getting secrets
2025-11-14T17:21:41.996+01:00 [app] DEBUG reqwest::connect: starting new connection: http://127.0.0.1:23269/
2025-11-14T16:21:42.082057Z DEBUG cargo_shuttle::provisioner_server: Received GET /projects/proj_LOCAL/resources/secrets
These secrets can be accessed by local service
┌────────────────────┐
│ Key                │
╞════════════════════╡
│ ADMIN_KEY          │
│ SERVER_PRIVATE_KEY │
└────────────────────┘

2025-11-14T16:21:42.087208Z DEBUG cargo_shuttle::provisioner_server: Received POST /projects/proj_LOCAL/resources
2025-11-14T17:21:42.087+01:00 [app]  INFO shuttle_runtime::rt: Provisioning DatabaseSharedPostgres
2025-11-14T17:21:42.087+01:00 [app] TRACE shuttle_runtime::rt: Checking state of DatabaseSharedPostgres
2025-11-14T16:21:42.087888Z TRACE cargo_shuttle::provisioner_server: getting sql string for project 'project-name'
2025-11-14T16:21:42.095532Z TRACE cargo_shuttle::provisioner_server: found container shuttle_project-name_shared_postgres
2025-11-14T16:21:42.095580Z TRACE cargo_shuttle::provisioner_server: shared_postgres container 'shuttle_project-name_shared_postgres' not running, so starting it
2025-11-14T16:21:45.904761Z TRACE cargo_shuttle::provisioner_server: waiting for 'shuttle_project-name_shared_postgres' to be ready for connections
2025-11-14T16:21:46.981761Z TRACE cargo_shuttle: Health check against runtime
2025-11-14T17:21:46.985+01:00 [app] TRACE shuttle_runtime::rt: Received health check
2025-11-14T17:21:46.986+01:00 [app] TRACE shuttle_runtime::rt: Responding to health check
2025-11-14T16:21:47.406879Z TRACE cargo_shuttle::provisioner_server: waiting for 'shuttle_project-name_shared_postgres' to be ready for connections

thread 'tokio-runtime-worker' panicked at /home/circleci/project/cargo-shuttle/src/provisioner_server.rs:261:18:
failed to create exec to check if container is ready: DockerResponseServerError { status_code: 409, message: "container 8c60d3395955bdabdd58065d04be5123b08c2181cb8486909d49800acad1881d is not running" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-11-14T17:21:48.788+01:00 [app] ERROR: Runtime Provisioning phase failed: error sending request for url (http://127.0.0.1:23269/projects/proj_LOCAL/resources)
Error: Runtime process exited with code 131

[jymchng]

Just saying installing version 0.56.0 to match the runtime in cargo.toml doesn't work.

[7ttp]

@jonaro00 @jymchng Could you please assign this issue to me? I’d like to work on a fix

[jymchng]

Hi @7ttp

Thank you for your interest but sadly I don't have the rights to assign you this ticket. Hope the Shuttle team can respond soon.