Noticed I have only 8Gb of space left at server, cleaned up - then noticed the version is outdated. Updated - and now farmer container can’t start, see error in logs:
subspace-node-1 | Error: SubstrateCli(Input(“Error opening spec file gemini-3c: No such file or directory (os error 2)”))
I use docker, Ubuntu 20.
Hi! Try updating --chain to gemini-3d in your compose file.
Looks like the docs didnt get updated, just got that fixed in the meantime here is the correct docker-compose file.
version: "3.7"
services:
node:
# For running on Aarch64 add `-aarch64` after `DATE`
image: ghcr.io/subspace/node:gemini-3d-2023-apr-18
volumes:
# Instead of specifying volume (which will store data in `/var/lib/docker`), you can
# alternatively specify path to the directory where files will be stored, just make
# sure everyone is allowed to write there
- node-data:/var/subspace:rw
# - /path/to/subspace-node:/var/subspace:rw
ports:
# If port 30333 or 30433 is already occupied by another Substrate-based node, replace all
# occurrences of `30333` or `30433` in this file with another value
- "0.0.0.0:30333:30333"
- "0.0.0.0:30433:30433"
restart: unless-stopped
command: [
"--chain", "gemini-3d",
"--base-path", "/var/subspace",
"--execution", "wasm",
"--blocks-pruning", "archive",
"--state-pruning", "archive",
"--port", "30333",
"--dsn-listen-on", "/ip4/0.0.0.0/tcp/30433",
"--rpc-cors", "all",
"--rpc-methods", "safe",
"--unsafe-ws-external",
"--dsn-disable-private-ips",
"--no-private-ipv4",
"--validator",
# Replace `INSERT_YOUR_ID` with your node ID (will be shown in telemetry)
"--name", "INSERT_YOUR_ID"
]
healthcheck:
timeout: 5s
# If node setup takes longer than expected, you want to increase `interval` and `retries` number.
interval: 30s
retries: 5
farmer:
depends_on:
node:
condition: service_healthy
# For running on Aarch64 add `-aarch64` after `DATE`
image: ghcr.io/subspace/farmer:gemini-3d-2023-apr-18
volumes:
# Instead of specifying volume (which will store data in `/var/lib/docker`), you can
# alternatively specify path to the directory where files will be stored, just make
# sure everyone is allowed to write there
- farmer-data:/var/subspace:rw
# - /path/to/subspace-farmer:/var/subspace:rw
ports:
# If port 30533 is already occupied by something else, replace all
# occurrences of `30533` in this file with another value
- "0.0.0.0:30533:30533"
restart: unless-stopped
command: [
"--base-path", "/var/subspace",
"farm",
"--disable-private-ips",
"--node-rpc-url", "ws://node:9944",
"--listen-on", "/ip4/0.0.0.0/tcp/30533",
# Replace `WALLET_ADDRESS` with your Polkadot.js wallet address
"--reward-address", "WALLET_ADDRESS",
# Replace `PLOT_SIZE` with plot size in gigabytes or terabytes, for example 100G or 2T (but leave at least 60G of disk space for node and some for OS)
"--plot-size", "PLOT_SIZE"
]
volumes:
node-data:
farmer-data:
Sorry, mixed farmer with node.
It ( --chain to gemini-3d) was there. But now I have this:
docker compose up -d
[+] Running 1/2
⠿ Container subspace-node-1 Error 2.0s
⠿ Container subspace-farmer-1 Recreated 0.1s
dependency failed to start: container subspace-node-1 is unhealthy
docker logs 501aeb4ecfed -f is (501aeb4ecfed - current hash of container):
2023-04-21 07:10:53 Subspace
2023-04-21 07:10:53 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:10:53 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:10:53 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:10:53 🏷 Node name: !da_blockchain2
2023-04-21 07:10:53 👤 Role: AUTHORITY
2023-04-21 07:10:53 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:10:53 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:10:54 Subspace
2023-04-21 07:10:54 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:10:54 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:10:54 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:10:54 🏷 Node name: !da_blockchain2
2023-04-21 07:10:54 👤 Role: AUTHORITY
2023-04-21 07:10:54 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:10:54 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:10:55 Subspace
2023-04-21 07:10:55 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:10:55 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:10:55 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:10:55 🏷 Node name: !da_blockchain2
2023-04-21 07:10:55 👤 Role: AUTHORITY
2023-04-21 07:10:55 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:10:55 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:10:56 Subspace
2023-04-21 07:10:56 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:10:56 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:10:56 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:10:56 🏷 Node name: !da_blockchain2
2023-04-21 07:10:56 👤 Role: AUTHORITY
2023-04-21 07:10:56 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:10:56 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:10:58 Subspace
2023-04-21 07:10:58 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:10:58 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:10:58 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:10:58 🏷 Node name: !da_blockchain2
2023-04-21 07:10:58 👤 Role: AUTHORITY
2023-04-21 07:10:58 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:10:58 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:11:00 Subspace
2023-04-21 07:11:00 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:11:00 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:11:00 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:11:00 🏷 Node name: !da_blockchain2
2023-04-21 07:11:00 👤 Role: AUTHORITY
2023-04-21 07:11:00 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:11:00 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:11:04 Subspace
2023-04-21 07:11:04 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:11:04 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:11:04 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:11:04 🏷 Node name: !da_blockchain2
2023-04-21 07:11:04 👤 Role: AUTHORITY
2023-04-21 07:11:04 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:11:04 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:11:11 Subspace
2023-04-21 07:11:11 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:11:11 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:11:11 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:11:11 🏷 Node name: !da_blockchain2
2023-04-21 07:11:11 👤 Role: AUTHORITY
2023-04-21 07:11:11 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:11:11 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:11:24 Subspace
2023-04-21 07:11:24 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:11:24 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:11:24 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:11:24 🏷 Node name: !da_blockchain2
2023-04-21 07:11:24 👤 Role: AUTHORITY
2023-04-21 07:11:24 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:11:24 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:11:50 Subspace
2023-04-21 07:11:50 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:11:50 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:11:50 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:11:50 🏷 Node name: !da_blockchain2
2023-04-21 07:11:50 👤 Role: AUTHORITY
2023-04-21 07:11:50 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:11:50 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
2023-04-21 07:12:42 Subspace
2023-04-21 07:12:42 ✌️ version 0.1.0-677ab36e108874ee84e79972b96814a0fecc0d24
2023-04-21 07:12:42 ❤️ by Subspace Labs <https://subspace.network>, 2021-2023
2023-04-21 07:12:42 📋 Chain specification: Subspace Gemini 3d
2023-04-21 07:12:42 🏷 Node name: !da_blockchain2
2023-04-21 07:12:42 👤 Role: AUTHORITY
2023-04-21 07:12:42 💾 Database: ParityDb at /var/subspace/chains/subspace_gemini_3d/paritydb/full
2023-04-21 07:12:42 ⛓ Native runtime: subspace-1 (subspace-0.tx0.au0)
I performed docker compose down - didn’t help.
Is there any other ways to reset node somehow? W/o cleaning all bases/plots.
subspace-node-1 is not what the node should be called using the standard compose in the official docs. Are you using a 3rd party docker-compose.yml? Can you share it please?
version: "3.7"
services:
node:
# For running on Aarch64 add `-aarch64` after `DATE`
image: ghcr.io/subspace/node:gemini-3d-2023-apr-18
volumes:
# Instead of specifying volume (which will store data in `/var/lib/docker`), you can
# alternatively specify path to the directory where files will be stored, just make
# sure everyone is allowed to write there
- node-data:/var/subspace:rw
# - /path/to/subspace-node:/var/subspace:rw
ports:
# If port 30333 or 30433 is already occupied by another Substrate-based node, replace all
# occurrences of `30333` or `30433` in this file with another value
- "0.0.0.0:30333:30333"
- "0.0.0.0:30433:30433"
restart: unless-stopped
command: [
"--chain", "gemini-3d",
"--base-path", "/var/subspace",
"--execution", "wasm",
"--blocks-pruning", "archive",
"--state-pruning", "archive",
"--port", "30333",
"--dsn-listen-on", "/ip4/0.0.0.0/tcp/30433",
"--rpc-cors", "all",
"--rpc-methods", "safe",
"--unsafe-ws-external",
"--dsn-disable-private-ips",
"--no-private-ipv4",
"--validator",
# Replace `INSERT_YOUR_ID` with your node ID (will be shown in telemetry)
"--name", "!da_blockchain2"
]
healthcheck:
timeout: 5s
# If node setup takes longer than expected, you want to increase `interval` and `retries` number.
interval: 30s
retries: 5
farmer:
depends_on:
node:
condition: service_healthy
# For running on Aarch64 add `-aarch64` after `DATE`
image: ghcr.io/subspace/farmer:gemini-3d-2023-apr-18
volumes:
# Instead of specifying volume (which will store data in `/var/lib/docker`), you can
# alternatively specify path to the directory where files will be stored, just make
# sure everyone is allowed to write there
- farmer-data:/var/subspace:rw
# - /path/to/subspace-farmer:/var/subspace:rw
ports:
# If port 30533 is already occupied by something else, replace all
# occurrences of `30533` in this file with another value
- "0.0.0.0:30533:30533"
restart: unless-stopped
command: [
"--base-path", "/var/subspace",
"farm",
"--disable-private-ips",
"--node-rpc-url", "ws://node:9944",
"--listen-on", "/ip4/0.0.0.0/tcp/30533",
# Replace `WALLET_ADDRESS` with your Polkadot.js wallet address
"--reward-address", "st8x34MosEbJ46S7ZRnvApZ9wvTvFVrCXTz9n3x6Kkff61KDR",
# Replace `PLOT_SIZE` with plot size in gigabytes or terabytes, for example 100G or 2T (but leave at least 60G of disk space for node and some for OS)
"--plot-size", "100G"
]
volumes:
node-data:
farmer-data:
And I use “docker compose” command instead of docker-compose if it matters (IDK why but I had probs with installation of docker-compose variant, but everything worked smooth till last days, I plotted some part of whole field according to last time my node was in telemetry, then I stopped to check and now I have this)
OK, your docker-compose.yml looks fine. The difference between the commands is that docker-compose is the old, deprecated way of invoking Docker Compose while docker compose is the new way which will be supported long term. I also use the latter so there are no problems there.
The fact that your node is coming up as subspace-node-1 is where I think your problem lies. I suspect you may have another node/farmer already running in Docker that you will need to stop and then try again.
You can see which containers you currently have setup by running docker ps. If you don’t find anything there, try docker ps -a on the end as that will show you containers that are created but not running. If you find an old container, check the docs but you’ll want something like docker container rm <container> to clear out an old one.
No, it always looks like this. I checked before and rechecked now - all the same thing 
Can it be some stuff in docker volumes? BTW in the docker volumes I have appropriate named folders:
Can you provide the output of docker ps -a?
I’m having this problem too; did he fix it?
COMMAND CREATED STATUS PORTS
NAMES
523bd97d21fd ghcr.io/subspace/farmer:gemini-3d-2023-apr-18 "/subspace-farmer --…" 29 hours ago Created
subspace-farmer-1
312256949fae ghcr.io/subspace/node:gemini-3d-2023-apr-18 "/subspace-node --ch…" 29 hours ago Restarting (132) 28 seconds ago
16eaeaa77b6e containrrr/watchtower:latest "/watchtower" 2 months ago Up 2 months 8080
/tcp
watchtower
Nope, I didn’t.………………………………
Can you provide your environment details please? I have just successfully run a node under Docker on Ubuntu 22.04 no problem. Could you also try docker compose down -v which will remove all your gemini-3c data by deleting the node and farmer data volumes.