@@ -140,9 +140,9 @@ docker run --detach \
140
140
-e CARDANO_SHELLEY_KES_KEY=/opt/cardano/config/keys/kes.skey \
141
141
-e CARDANO_SHELLEY_OPERATIONAL_CERTIFICATE=/opt/cardano/config/keys/node.cert \
142
142
-e CARDANO_SHELLEY_VRF_KEY=/opt/cardano/config/keys/vrf.skey \
143
- -v /src /cardano/node-keys:/opt/cardano/config/keys \
144
- -v /src /cardano/node-db:/data/db \
145
- -v /src /cardano/node-ipc:/ipc \
143
+ -v /srv /cardano/node-keys:/opt/cardano/config/keys \
144
+ -v /srv /cardano/node-db:/data/db \
145
+ -v /srv /cardano/node-ipc:/ipc \
146
146
-p 3001:3001 \
147
147
-p 12798:12798 \
148
148
ghcr.io/blinklabs-io/cardano-node run
@@ -161,9 +161,9 @@ docker run --detach \
161
161
-e CARDANO_SHELLEY_KES_KEY=/opt/cardano/config/keys/kes.skey \
162
162
-e CARDANO_SHELLEY_OPERATIONAL_CERTIFICATE=/opt/cardano/config/keys/node.cert \
163
163
-e CARDANO_SHELLEY_VRF_KEY=/opt/cardano/config/keys/vrf.skey \
164
- -v /src /cardano/node-keys:/opt/cardano/config/keys \
165
- -v /src /cardano/node-db:/data/db \
166
- -v /src /cardano/node-ipc:/ipc \
164
+ -v /srv /cardano/node-keys:/opt/cardano/config/keys \
165
+ -v /srv /cardano/node-db:/data/db \
166
+ -v /srv /cardano/node-ipc:/ipc \
167
167
-p 3001:3001 \
168
168
-p 12798:12798 \
169
169
ghcr.io/blinklabs-io/cardano-node run
@@ -193,9 +193,9 @@ for any reason. This will also cause the container to automatically restart
193
193
after a host reboot, so long as Docker is configured to start on boot. We
194
194
set variables to configure a block producer and pass the paths to the 3 keys
195
195
we need. Our node's persistent data and client communication socket are mapped
196
- to ` /src /cardano/node-db ` and ` /src /cardano/node-ipc ` on the host,
196
+ to ` /srv /cardano/node-db ` and ` /srv /cardano/node-ipc ` on the host,
197
197
respectively. This allows for running applications directly on the host which
198
- may need access to these. We also map ` /src /cardano/node-keys ` on the host to
198
+ may need access to these. We also map ` /srv /cardano/node-keys ` on the host to
199
199
a path within the container to support running as a block producer. Last, we
200
200
add mapping the host's port 12798 to the container 12798, which is the port for
201
201
exposing the node's metrics in Prometheus format, for monitoring.
0 commit comments