larsks / docker-image-logitech-media-server

MIT License
33 stars 74 forks source link

oci runtime error: container_linux.go:235: starting container process caused "container init exited prematurely" #24

Open Chaz6 opened 5 years ago

Chaz6 commented 5 years ago

Host: CentOS 7.6 64bit

sudo docker run -d --rm --init \
           -p 192.168.1.100:9000:9000 \
           -p 192.168.1.100:9090:9090 \
           -p 192.168.1.100:3483:3483 \
           -p 192.168.1.100:3483:3483/udp \
           -v /etc/localtime:/etc/localtime:ro,Z \
           -v /home/srv.squeezebox/state:/srv/squeezebox:Z \
           -v /home/srv.squeezebox/music:/srv/music:Z \
           larsks/logitech-media-server
b71d846713f04e63616cfef11601ba14e035ba8b8960661bda11c69eea4aa41f
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:235: starting container process caused "container init exited prematurely".

I could not find anything useful in the system logs. Do you have any ideas why it is failing, or how I can debug it further?

akr8s commented 4 years ago

Hey man, have you made any progress on this issue?

Chaz6 commented 4 years ago

Hey man, have you made any progress on this issue?

Sorry I have not touched it since. I will have another try this evening and report back.

chavalisailaja commented 4 years ago

while running the php container using ansible-operator on openshift, am facing the issue given below: Error: failed to start container "php": Error response from daemon: oci runtime error: container_linux.go:235: starting container process caused "container init exited prematurely" Can you please help me? why it is getting? and what is the solution

harshblog150 commented 4 years ago

same error, any one knows the fix.

lichban commented 4 years ago

looks like this could be a error for multiple events. I found that my problem was a volume mount that had a problem

sybrandy commented 4 years ago

I just had this error this morning. In my case, I had a volume mount that referenced a file directly and I accidentally moved the file to a different directory. So yeah, don't do that.

Not sure if there was a better way to fix the issue, but I ended up recreating the container.