Process: 10391 ExecStart=/usr/bin/dockerd -H fd:// -containerd=/run/contai> Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor pr>Īctive: failed (Result: exit-code) since Wed 11:10:58 IST 15s > rvice - Docker Application Container Engine.
See "systemctl status rvice" and "journalctl -xe" for details.Īnd then systemctl status rvice I got I ran systemctl start docker command and got Job for rvice failed because the control process exited with error code. └─atomicos-docker-pool 253:3 0 2.I'm using Fedora release 33 (Thirty Three)ĭocker version is Docker version 20.10.0, build 7287ab3įirst I ran docker system prune and since then docker daemon failed to start. └─atomicos-docker-pool_tdata 253:2 0 2.7G 0 lvm ├─atomicos-docker-pool_tmeta 253:1 0 12M 0 lvm ├─atomicos-root 253:0 0 3G 0 lvm /sysroot
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convertĭocker-pool atomicos twi-a-t- 2.68g 0.71 0.33 Time="T15:25:52.960602241Z" level=warning msg="could not change group /var/run/docker.sock to docker: group docker not found" Main PID: 806 (code=exited, status=1/FAILURE) Process: 806 ExecStart=/usr/bin/dockerd-current -add-runtime docker-runc=/usr/libexec/docker/docker-runc-current -default-runtime=docker-runc -exec-opt native.cgroupdriver=systemd -userland-proxy-path=/usr/libexec/docker/docker-proxy-current -seccomp-profile=/etc/docker/seccomp.json $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES (code=exited, status=1/FAILURE) Last login: Mon May 21 15:22:08 2018 from ~]$ sudo su -Īctive: failed (Result: exit-code) since Mon 15:25:53 UTC 9min ago Go ahead and execute manually the daemon run command and check whether problems will be reported or not: sudo -u icingavspheredb /usr/bin/icingacli vspheredb daemon run You should also check the environment files for existence and set environments manually before executing the command above (if any are present). Maybe not.Ĭonnection to 192.168.121.193 closed by remote host. Whether they are specific to Fedora, specific to CentOS, or specific to RHELAH and need their own BZ. To me this is as good a place as any to "route" issues and find the most effective way to get them resolved. That said it's definitely possible with some of these things that it's CentOS-AH specific as some of the metadata gets important. This fix needs to go through the whole downstream thing.įor the pool issue.I think that deserves a bug against docker in RHEL? Though of course that sort of wants to have reproduced it against RHELAH first. For me things get too easily lost in bugzilla.Īnyways is the Fedora version of the first one. Filing issues here helps bring awareness to the issues I believe. You are right, but I think it's mostly a philosophical question. In general, I'm not sure about filing atomic-wg issues that relate to CentOS because we can't generally fix them without going through RHEL, right? We probably need to address these issues. Time="T01:30:26.499243981Z" level=info msg="libcontainerd: new containerd process, pid: 925"Įrror starting daemon: error initializing graphdriver: devicemapper: Non existing device atomicos-docker-poolĭrvice: main process exited, code=exited, status=1/FAILUREįailed to start Docker Application Container Engine.
Time="T01:30:26.496375725Z" level=warning msg="could not change group /var/run/docker.sock to docker: group docker not found" Starting Docker Application Container Engine. Main PID: 795 (code=exited, status=1/FAILURE) Process: 795 ExecStart=/usr/bin/dockerd-current -add-runtime docker-runc=/usr/libexec/docker/docker-runc-current -default-runtime=docker-runc -exec-opt native.cgroupdriver=systemd -userland-proxy-path=/usr/libexec/docker/docker-proxy-current -seccomp-profile=/etc/docker/seccomp.json $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES (code=exited, status=1/FAILURE) Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)ĭrop-In: /usr/lib/systemd/system/Īctive: failed (Result: exit-code) since Wed 01:30:27 UTC 9min ago bash-4.2# systemctl status docker -o cat | tee
0 kommentar(er)
