You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marc Roos <M....@f1-outsourcing.eu> on 2019/08/19 19:47:01 UTC
"Failed to launch container" "No such file or directory"
Some temp folders gone? How to resolve this?
Failed to launch container: Failed to read manifest from
'/tmp/mesos/store/docker/layers/8c49e24d4aba93c77354143366e2427e0e2e7191
cb85dbc1aa187e4e480021c1/json': No such file or directory
BUG /tmp/mesos losing files add /usr/lib/tmpfiles.d/mesos.conf
Posted by Marc Roos <M....@f1-outsourcing.eu>.
For the developers, tmp in centos6/7 (and probably more distros) is
being cleaned automatically! Read this:
https://www.thegeekdiary.com/centos-rhel-67-why-the-files-in-tmp-directory-gets-deleted-periodically/
https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/
, maybe add something like this file to your rpms.
cat << EOF >> /usr/lib/tmpfiles.d/mesos.conf
x /tmp/mesos/store/docker/
EOF
Now mesos fails often even when being used with "forcePullImage": true
I am having this error:
Task id
chat_openfire.instance-5c6ba784-d7a7-11e9-b799-0050563001a1._app.11
State
TASK_FAILED
Message
Failed to launch container: Failed to read manifest from
'/tmp/mesos/store/docker/layers/8c49e24d4aba93c77354143366e2427e0e2e7191
cb85dbc1aa187e4e480021c1/json': No such file or directory
mesos-1.8.1-2.0.1.el7.x86_64
-----Original Message-----
From: Marc Roos
Sent: maandag 19 augustus 2019 21:47
To: user
Subject: "Failed to launch container" "No such file or directory"
Some temp folders gone? How to resolve this?
Failed to launch container: Failed to read manifest from
'/tmp/mesos/store/docker/layers/8c49e24d4aba93c77354143366e2427e0e2e7191
cb85dbc1aa187e4e480021c1/json': No such file or directory
RE: "Failed to launch container" "No such file or directory" /tmp files are being cleaned
Posted by Marc Roos <M....@f1-outsourcing.eu>.
Hmmm, I have deleted layers there, now it seems ok and the image is
pulled from the nfs share.
1. should the forced pull not be forcing to get the image regardless
what is in /tmp?
2. I think from centos7 /tmp is not cleared just after a reboot, but
also scheduled. So maybe not such a good place to store docker layers?
-----Original Message-----
From: Marc Roos
Sent: maandag 19 augustus 2019 21:47
To: user
Subject: "Failed to launch container" "No such file or directory"
Some temp folders gone? How to resolve this?
Failed to launch container: Failed to read manifest from
'/tmp/mesos/store/docker/layers/8c49e24d4aba93c77354143366e2427e0e2e7191
cb85dbc1aa187e4e480021c1/json': No such file or directory