ERROR: for xibo_cms-xmr_1 Cannot start service cms-xmr: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:297:

Hello!

After: sudo docker-compose -f cms_custom-ports.yml up -d

I get this error:
Starting xibo_cms-db_1 …
Starting xibo_cms-xmr_1 …
Starting xibo_cms-xmr_1
Starting xibo_cms-xmr_1 … error

ERROR: for xibo_cms-xmr_1 Cannot start service cms-xmr: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknoStarting xibo_cms-db_1 … error

ERROR: for xibo_cms-db_1 Cannot start service cms-db: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown

ERROR: for cms-db Cannot start service cms-db: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown

ERROR: for cms-xmr Cannot start service cms-xmr: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown
ERROR: Encountered errors while bringing up the project.

How can you solve the problem?

THANKS!

Hello!

Does really nobody have a solution or tip for my problem? Unfortunately, I can not update Xibo content for months now, because I can not reach the admin page. I tried everything I found, but unfortunately without success. Does anyone have any idea how I could fix the problem?!?!

I am at the end of my knowledg and if i can not find any soluition i have to stop the project Xibo …

SO PLAESE - PLEASE - PLEASE - PLEASE - PLEASE GIVE ME SOME HELP.

THANKS!!!

After uninstall (purge) Docker and reinstall the latest Docker Version, I get this message vom Xibo in my terminal:

opt/xibo$ sudo docker-compose -f cms_custom-ports.yml up -d
Removing xibo_cms-db_1
Removing xibo_cms-xmr_1
Recreating 60b8b3465a82_xibo_cms-db_1 … error
Recreating 8fe6ac60bcc9_xibo_cms-xmr_1 …

ERROR: for 60b8b3465a82_xibo_cms-db_1 Cannot start service cms-db: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:297: copying bootstrap data to pipe causedRecreating 8fe6ac60bcc9_xibo_cms-xmr_1 … error

ERROR: for 8fe6ac60bcc9_xibo_cms-xmr_1 Cannot start service cms-xmr: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown

ERROR: for cms-db Cannot start service cms-db: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown

ERROR: for cms-xmr Cannot start service cms-xmr: OCI runtime create failed: container_linux.go:348: starting container process caused “process_linux.go:297: copying bootstrap data to pipe caused “write init-p: broken pipe””: unknown
ERROR: Encountered errors while bringing up the project.

… any ideas ?

It’s an error message from Docker not from Xibo. You’re likely to get better help for Docker issues posting on the Docker forums.

In general, errors like that are caused by old/broken Docker versions, or something specific to your environment, but you’ve given us no information about what OS you’ve got this installed on, or what hardware, so it’s nearly impossible to help you I’m afraid.

You don’t say if this was a working install that stopped working, or if it has never worked. The more information and context you give the better.

I’d also suggest you post the output of docker ps as a minimum.

Hi Alex - THANK YOU FOR YOUR ANSWER!!!

  1. OS: Ubuntu 14.04 LTS

  2. sudo docker ps
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
    … thats all

  3. Xibo / Docker System was working perfekt from September 2018 upto Februar 2019.

  4. I don’t know whats happend in Februar 2019. To my mind i have changes nothing. Maybe a power outage or a standard Ubuntu update affecting the functionality of Docker?

55/5000

Will this information help solve the problem?

Solution: The kernel of 14.04 did not work anymore with the current Docker version, after an update to 18.04 the Xibo Admin is running again.

Ubuntu 14.04 has been out of support for some time now, so if you’re still using it you should be looking to upgrade to 16.04 or 18.04 in any case :slight_smile: