LoginSignup
0
1

More than 3 years have passed since last update.

[対処法メモ]OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449:

Posted at

発生事象

selenium/standalone-chrome-debugを起動しようとしたところエラー発生。

root@host# docker run -d -p 4444:4444 selenium/standalone-chrome-debug
98a864e9266402fbf327f12eaeb6562dd030db9e0d7ffeeb7cd384a5e3e2f9bb

docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: 
starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: 
running prestart hook 0 caused \\\"error running hook: exit status 127, stdout: , 
stderr: Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 540: elf_machine_rela_relative: 
Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed!\\\\n\\\"\"": unknown.

対処法

調べた限りではdocker system prune後、dockerサービス再起動で問題ないはずだがエラーとなったためマシン再起動

root@host# docker system prune
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all dangling images
  - all dangling build cache

Are you sure you want to continue? [y/N] y
Deleted Containers:
98a864e9266402fbf327f12eaeb6562dd030db9e0d7ffeeb7cd384a5e3e2f9bb
d25b38ddf4917adfcf8d5bc64b32ba4cac17f5343ab89129b77454dc40d20b60

Deleted Images:
deleted: sha256:c2053572c0a2b182002422142d7cd1c8b899616e2016fc3aa5aecbdfdfb71b35
deleted: sha256:82e73d114a144feabbb0dd15804d16a94fde3f35900dd02cbf8e9ff33c2fbf93
deleted: sha256:ba8cdecd4a6a36e1265e8a2235341c90178726926c4046a77fd201cf104cf3b6

Total reclaimed space: 14.92GB

root@host# /etc/init.d/docker restart
[....] Restarting docker (via systemctl): docker.serviceJob for docker.service f              ailed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
 failed!
root@host# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e
   Active: failed (Result: exit-code) since Wed 2020-05-13 09:43:13 JST; 17s ago
     Docs: https://docs.docker.com
  Process: 32173 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/container
 Main PID: 32173 (code=exited, status=127)

 5月 13 09:43:11 host systemd[1]: Starting Docker Application Container Engin
 5月 13 09:43:11 host systemd[1]: docker.service: Main process exited, code=e
 5月 13 09:43:11 host systemd[1]: docker.service: Failed with result 'exit-co
 5月 13 09:43:11 host systemd[1]: Failed to start Docker Application Containe
 5月 13 09:43:13 host systemd[1]: docker.service: Service RestartSec=2s expir
 5月 13 09:43:13 host systemd[1]: docker.service: Scheduled restart job, rest
 5月 13 09:43:13 host systemd[1]: Stopped Docker Application Container Engine
 5月 13 09:43:13 host systemd[1]: docker.service: Start request repeated too
 5月 13 09:43:13 host systemd[1]: docker.service: Failed with result 'exit-co
 5月 13 09:43:13 host systemd[1]: Failed to start Docker Application Containe
lines 1-17/17 (END)
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-05-13 09:43:13 JST; 17s ago
     Docs: https://docs.docker.com
  Process: 32173 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.s
 Main PID: 32173 (code=exited, status=127)

root@host# reboot

対処後、正常起動を確認

root@host# docker run -d -p 4444:4444 selenium/standalone-chrome-debug
e78f73ce77e467723d19fa37bd7e35ac375f36b25cdd92f09fbafa8227a69794
root@host#
0
1
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
1