Failed DNS resolution:
- If you encounter the following error:
Jan 18 12:48:03 node1 portworx: level=error msg="error in obtaining etcd version: \ Get http://_some_host:2379/version: dial tcp: lookup _some_host on [::1]:53: dial udp \ [::1]:53: connect: no route to host"
- Please ensure that the
NetworkManagerservice has been stopped and disabled on your Linux host system.
Portworx processes running inside OCI container must be able to perform the DNS hostname resolution, especially if using hostnames for KVDB configuration, or the CloudSnap feature. However, host’s
NetworkManagerservice can update the DNS configuration (the
/etc/resolv.conffile) after the Portworx container has started, and such changes will not propagate from host to container.
Failure to install Portworx:
- You may have experienced the following issue installing Portworx (e.g. Fedora 28 host)
# sudo docker run --entrypoint /runc-entry-point.sh --rm -i --name px-installer --privileged=true \ -v /etc/pwx:/etc/pwx -v /opt/pwx:/opt/pwx portworx/px-base-enterprise:2.1.2 docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting \ container process caused "process_linux.go:430: container init caused \ \"write /proc/self/attr/keycreate: permission denied\"": unknown.
This error is a docker issue (see moby#39109), and it prevents running even the simplest containers:
# sudo docker run --rm -it hello-world docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting \ container process caused "process_linux.go:430: container init caused \ \"write /proc/self/attr/keycreate: permission denied\"": unknown.
- to work around this issue, one should either turn off the SELinux support, or make sure to use docker-package provided by the host’s platform.
Last edited: Tuesday, Apr 7, 2020
Questions? Visit the Portworx forum.