# Docker error "dependency failed to start: container subspace-node-1 is unhealthy" **URL:** \ **Category:** Support\ **Tags:** gemini, error\ **Created:** [November 4, 2023, 6:40am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114 "2023-11-04T06:40:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![bigmotor](https://avatars.discourse-cdn.com/v4/letter/b/e95f7d/32.png) [@bigmotor](https://forum.autonomys.xyz/u/bigmotor)\ **Post date:** [November 4, 2023, 6:40am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/1 "2023-11-04T06:40:43Z")
## Issue Report ### Environment - **Operating System:** ubuntu - **Pulsar/Advanced CLI/Docker:** Advanced CLI ### Problem ```auto sudo docker compose up -d [+] Running 2/2 ✘ Container subspace-node-1 Error 2.8s ✔ Container subspace-farmer-1 Recreated 0.0s dependency failed to start: container subspace-node-1 is unhealthy ``` I get this error when I follow the docs ```auto Version: 0.1.0-22d5e48b0465b3634996b6fd9bdc29447a971a15 0: sp_panic_handler::set::{{closure}} 1: std::panicking::rust_panic_with_hook 2: std::panicking::begin_panic_handler::{{closure}} 3: std::sys_common::backtrace::__rust_end_short_backtrace 4: rust_begin_unwind 5: core::panicking::panic_fmt 6: fdlimit::raise_fd_limit 7: subspace_node::main 8: std::sys_common::backtrace::__rust_begin_short_backtrace 9: main 10: __libc_start_main 11: _start Thread 'main' panicked at 'raise_fd_limit: error calling setrlimit: Operation not permitted (os error 1)', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fdlimit-0.2.1/src/lib.rs:105 This is a bug. Please report it at: ``` this is logs of docker logs subspace-node-1 ```auto [Paste any errors or relevant logs here] ``` ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [November 5, 2023, 1:25am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/2 "2023-11-05T01:25:25Z")
That is interesting, I have not seen it before. Can you post `docker-compose.yml` contents? There must be something in Docker configuration or the environment that prevents that operation from working. Also if you can add `RUST_BACKTRACE=full` environment variable it might print something more useful in the backtrace or else I can help you with test build to debug this further. ---
**Author:** ![bigmotor](https://avatars.discourse-cdn.com/v4/letter/b/e95f7d/32.png) [@bigmotor](https://forum.autonomys.xyz/u/bigmotor)\ **Post date:** [November 5, 2023, 1:35am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/3 "2023-11-05T01:35:14Z")
this is my docker-compose.yml ```auto version: "3.7" services: node: image: ghcr.io/subspace/node:gemini-3g-2023-nov-03 volumes: - node-data:/var/subspace:rw ports: - "0.0.0.0:30333:30333/udp" - "0.0.0.0:30333:30333/tcp" - "0.0.0.0:30433:30433/udp" - "0.0.0.0:30433:30433/tcp" restart: unless-stopped command: [ "--chain", "gemini-3g", "--base-path", "/var/subspace", "--blocks-pruning", "256", "--state-pruning", "archive-canonical", "--port", "30333", "--dsn-listen-on", "/ip4/0.0.0.0/udp/30433/quic-v1", "--dsn-listen-on", "/ip4/0.0.0.0/tcp/30433", "--rpc-cors", "all", "--rpc-methods", "unsafe", "--rpc-external", "--no-private-ipv4", "--validator", "--name", "subspace" ] healthcheck: timeout: 5s interval: 30s retries: 600 farmer: depends_on: node: condition: service_healthy image: ghcr.io/subspace/farmer:gemini-3g-2023-nov-03 volumes: - farmer-data:/var/subspace:rw ports: - "0.0.0.0:30533:30533/udp" - "0.0.0.0:30533:30533/tcp" restart: unless-stopped command: [ "farm", "--node-rpc-url", "ws://node:9944", "--listen-on", "/ip4/0.0.0.0/udp/30533/quic-v1", "--listen-on", "/ip4/0.0.0.0/tcp/30533", "--reward-address", "st9mKkKrtPb9kYwPpZpcev6C8b2o65YekjcoXeFT9Fn41ucSs", "path=/var/subspace,size=400G" ] volumes: node-data: farmer-data: ``` ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [November 5, 2023, 1:51am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/4 "2023-11-05T01:51:21Z")
Okay, so those are recommended options, shouldn’t cause issues. What Ubuntu version are you running this on and did you customize anything on it? ---
**Author:** ![bigmotor](https://avatars.discourse-cdn.com/v4/letter/b/e95f7d/32.png) [@bigmotor](https://forum.autonomys.xyz/u/bigmotor)\ **Post date:** [November 5, 2023, 1:54am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/5 "2023-11-05T01:54:21Z")
Ubuntu 20.04.6 LTS and no customize ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [November 5, 2023, 2:12am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/6 "2023-11-05T02:12:49Z")
> [@bigmotor](#): > > `Operation not permitted (os error 1)` Did you install Docker itself from stock repository or from Docker’s (as in [Install Docker Engine on Ubuntu | Docker Docs](https://docs.docker.com/engine/install/ubuntu/))? ---
**Author:** ![bigmotor](https://avatars.discourse-cdn.com/v4/letter/b/e95f7d/32.png) [@bigmotor](https://forum.autonomys.xyz/u/bigmotor)\ **Post date:** [November 5, 2023, 2:19am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/7 "2023-11-05T02:19:23Z")
maybe like this command ```auto sudo apt install docker-ce docker-ce-cli containerd.io ``` ---
**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\ **Post date:** [November 5, 2023, 2:44am UTC](https://forum.autonomys.xyz/t/docker-error-dependency-failed-to-start-container-subspace-node-1-is-unhealthy/2114/8 "2023-11-05T02:44:42Z")
Hm, “maybe” isn’t very accurate. Can you check if you have `docker-ce` or `docker.io` installed? Either way it shouldn’t crash, I have submitted [Catch panic generated by `fdlimit` call by nazar-pc · Pull Request #2155 · paritytech/polkadot-sdk · GitHub](https://github.com/paritytech/polkadot-sdk/pull/2155) to fix it and we’ll pull into one of the future Subspace limits. Without that you need to figure out why Docker doesn’t allow your container to change file descriptor limits, this is what is failing there.