This is the error reported to start the container, docker logs is not, the container is created, but can not start the container
Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused “process_linux.go:449: container init caused “rootfs_linux.go:58: mounting \”/etc/timezone\” to rootfs \”/var/lib/docker/overlay2/132f5ea82c98a1206ccb13e13f06c96737036c722c290e989b462c2d77458a8f/merged\” at \”/var/lib/docker/overlay2/132f5ea82c98a1206ccb13e13f06c96737036c722c290e989b462c2d77458a8f/merged/etc/timezone\” caused \“not a directory\”””: unknown: Are you trying to mount a directory onto a file (or vice-versa)?Check if the specified host path exists and is the expected type
Error: failed to start containers: 6e3a9e751884
Check that it is a mapping problem, after checking that the host does not have a directory to be mapped, create the directory and the container will start normally.

Similar Posts:

• failed: OCI runtime create failed: container_linux.go:348
• Docker OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caus
• [Solved] OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: “/bin/bash”: stat /bin/bash: no such file or directory: unknown
• [Solved] OCI runtime exec failed……executable file not found in $PATH”: unknown
• Docker Container Error:Failed to get D-Bus connection: Operation not permitted
• How to Solve docker run Error: oci runtime error
• Docker Container Performance Monitoring Tool: google/cadvisor
• Job for docker.service failed because the control process exited with error code. See “syste…
• Install a docker container in centos7 that can log in SSH
• [Solved] Docker Container Start Error: OCI runtime create failed: container with ID exists