You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Philip Winder (JIRA)" <ji...@apache.org> on 2016/07/29 07:53:20 UTC
[jira] [Updated] (MESOS-5927) Unable to run "scratch" Dockerfiles
with Unified Containerizer
[ https://issues.apache.org/jira/browse/MESOS-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Winder updated MESOS-5927:
---------------------------------
Description:
It is not possible to run Docker containers that are based upon the "scratch" container.
Setup: Mesos 1.0.0 with the following Mesos settings:
{code:bash}
echo 'docker' | sudo tee /etc/mesos-slave/image_providers
echo 'filesystem/linux,docker/runtime' | sudo tee /etc/mesos-slave/isolation
{code}
Recreate: From a Master or Slave, run:
{code:bash}
mesos-execute --command='echo ok' --docker_image=hello-seattle --master=localhost:5050 --name=test
{code}
Effect: The container will crash with messages from Mesos reporting it can't mount folder x/y/z. E.g. can't mount /tmp. This means you can't run any container that is not a "fat" container (i.e. one with a full OS). E.g. error:
bq. Failed to enter chroot '/var/lib/mesos/provisioner/containers/fed6add8-0126-40e6-ae81-5859a0c1a2d4/backends/copy/rootfses/4feefc8b-fd5a-4835-95db-165e675f11cd': /tmp in chroot does not existI0729 07:49:56.753474 4362 exec.cpp:413] Executor asked to shutdown
Expected: Run without issues.
Use case: We use scratch based containers with static binaries to keep the image size down. This is a common practice.
was:
It is not possible to run Docker containers that are based upon the "scratch" container.
Setup: Mesos 1.0.0 with the following Mesos settings:
```
echo 'docker' | sudo tee /etc/mesos-slave/image_providers
echo 'filesystem/linux,docker/runtime' | sudo tee /etc/mesos-slave/isolation
```
Recreate: From a Master or Slave, run something to the effect of:
`mesos-execute --command='echo ok' --docker_image=scratch --master=$MASTER:5050`
Effect: The container will crash with messages from Mesos reporting it can't mount folder x/y/z. E.g. can't mount /tmp. This means you can't run any container that is not a "fat" container (i.e. one with a full OS).
Expected: Run without issues.
Use case: We use scratch based containers with static binaries to keep the image size down. This is a common practice.
> Unable to run "scratch" Dockerfiles with Unified Containerizer
> --------------------------------------------------------------
>
> Key: MESOS-5927
> URL: https://issues.apache.org/jira/browse/MESOS-5927
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.0.0
> Reporter: Philip Winder
>
> It is not possible to run Docker containers that are based upon the "scratch" container.
> Setup: Mesos 1.0.0 with the following Mesos settings:
> {code:bash}
> echo 'docker' | sudo tee /etc/mesos-slave/image_providers
> echo 'filesystem/linux,docker/runtime' | sudo tee /etc/mesos-slave/isolation
> {code}
> Recreate: From a Master or Slave, run:
> {code:bash}
> mesos-execute --command='echo ok' --docker_image=hello-seattle --master=localhost:5050 --name=test
> {code}
> Effect: The container will crash with messages from Mesos reporting it can't mount folder x/y/z. E.g. can't mount /tmp. This means you can't run any container that is not a "fat" container (i.e. one with a full OS). E.g. error:
> bq. Failed to enter chroot '/var/lib/mesos/provisioner/containers/fed6add8-0126-40e6-ae81-5859a0c1a2d4/backends/copy/rootfses/4feefc8b-fd5a-4835-95db-165e675f11cd': /tmp in chroot does not existI0729 07:49:56.753474 4362 exec.cpp:413] Executor asked to shutdown
> Expected: Run without issues.
> Use case: We use scratch based containers with static binaries to keep the image size down. This is a common practice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)