I’m trying to set up cardano in Kubernetes and cardano-db-sync fails.
[db-sync-node.Subscription:Notice:1322] [2021-06-26 14:53:44.18 UTC] Identity Connection Attempt Start, destination LocalAddress "/ipc/node.socket" [db-sync-node.Subscription:Error:1322] [2021-06-26 14:53:44.18 UTC] Identity Connection Attempt Exception, destination LocalAddress "/ipc/node.socket" exception: Network.Socket.connect: <socket: 14>: does not exist (Connection refused) [db-sync-node.ErrorPolicy:Warning:4] [2021-06-26 14:53:44.18 UTC] IP LocalAddress "/ipc/node.socket" ErrorPolicySuspendPeer (Just (ConnectionExceptionTrace Network.Socket.connect: <socket: 14>: does not exist (Connection refused))) 20s 20s [db-sync-node.Subscription:Warning:45] [2021-06-26 14:53:44.21 UTC] Identity Failed to start all required subscriptions
/ipc/node.socket exists in cardano-db-sync’s pod. I also have transaction & relay nodes running in different pods and working fine.
Hi!
Which docker image are you using?
opened 08:26AM - 09 Feb 21 UTC
closed 12:20PM - 08 Jun 21 UTC
bug
**Internal/External**
*External*
**Area**
*Docker*
**Summary**
Th… e instructions documented [here](https://hub.docker.com/r/inputoutput/cardano-node) do not work when the IPC socket location is not mapped to a volume.
**Steps to reproduce**
This works ...
```
docker run --rm \
-v ipc:/ipc \
-e NETWORK=mainnet \
inputoutput/cardano-node
```
This fails ...
```
docker run --rm \
-e NETWORK=mainnet \
inputoutput/cardano-node
cardano-node: Network.Socket.bind: does not exist (No such file or directory)
```
**System info (please complete the following information):**
- OS: Debian
- Version: 10
- Node version: 1.25.1
**Additional context**
You can leave it to me, I'll provide a fix.
Tried with 10.0.0 and still same issue.
so do you have a link to the image?
and how do you run the image?
I’m using this image Docker Hub
image: "<custom-image-from-the-above>"
args: [
"--config", "/config/cardano-db-sync/config.json",
"--socket-path", "/ipc/node.socket",
"--state-dir", "/data"
config file added in the custom image during on build
socket file is from persistent volume (same one used from relay & transaction nodes)
data dir is currently a volume on the node (plan is to use pv as well)
1 Like