search

w3f / polkadot-deployer

Tool for deploying polkadot networks
Apache License 2.0
100 stars 45 forks source link

in docker cmd and private registry #81

Open martinfridrich opened 4 years ago

martinfridrich commented 4 years ago

Hi, is there a way to specify cmd/binary which will be run in docker image and credentials for private docker registry? thanks

fgimenez commented 4 years ago

The helm chart used for installing polkadot has a config option for specifying the cmd/binary to use https://github.com/w3f/polkadot-charts/blob/master/charts/polkadot/templates/statefulset.yaml#L85, but it is not currently available from polkadot-deployer, it should be easy to add it in this function https://github.com/w3f/polkadot-deployer/blob/master/lib/clients/helm.js#L186

It is not possible at the moment to specify the image pull secret for pulling from a private registry.

martinfridrich commented 4 years ago

Thank you. I've tried to change docker image and binary and it's stuck at: 

polkadot-node-1-session-injection-qtx22   0/1     ContainerCreating   0          0s
polkadot-node-1-session-injection-qtx22   1/1     Running             0          2s
polkadot-node-0-session-injection-brchs   0/1     Pending             0          0s
polkadot-node-0-session-injection-brchs   0/1     Pending             0          0s
polkadot-node-0-session-injection-brchs   0/1     ContainerCreating   0          0s
polkadot-node-1-session-injection-qtx22   0/1     Error               0          3s
polkadot-node-0-session-injection-brchs   1/1     Running             0          1s
polkadot-node-0-session-injection-brchs   0/1     Error               0          2s

Is there a way to turn on more verbose logging ?(k8s, helm,...) I'm trying local deployment with --verbose flag thanks

fgimenez commented 4 years ago

The session injection job should keep restarting for a while until the nodes are ready and it can perform the proper RPC call, so getting some errors and restarts is normal. If it keeps running too long (more than ~2min) then you should check the node(s) logs:

$ kind get kubeconfig --name <your_project_name> > ./kc
$ export KUBECONFIG=./kc
$ kubectl logs -n <your_project_name> polkadot-node-0-0

being <your_project_name> the name field in your config. You need to have kind installed https://kind.sigs.k8s.io/docs/user/quick-start/ or use the b binary shipped with polkadot-deployer (in linux under ~/.config/polkadot-deployer/components/kind)