[
https://issues.apache.org/jira/browse/MESOS-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avinash Sridharan updated MESOS-5277:
-------------------------------------
Description:
Some Dockerfiles run the `rm` command to remove files from the base image using
the "RUN" directive in the Dockerfile. An example can be found here:
https://github.com/ngineered/nginx-php-fpm.git
In the final rootfs the removed files should not be present. Presence of these
files in the final image can make the container misbehave. For example, the
nginx-php-fpm docker image that is referenced tries to remove the default nginx
config and replaces it with its own config to point to a different HTML root.
If the default nginx config is still present after the building the image,
nginx will start pointing to a different HTML root than the one set in the
Dockerfile.
Currently the copy backend cannot handle removal of files from intermediate
layers. This can cause issues with docker images built using a Dockerfile
similar to the one listed here. Hence, we need to add REMOVE semantics to the
copy backend.
was:
Some Dockerfile run the `rm` command to remove files from the base image using
the "RUN" directive in the Dockerfile. An example can be found here:
https://github.com/ngineered/nginx-php-fpm.git
In the final rootfs the removed files should not be present. Presence of these
files in the final image can make the container misbehave. For example, the
nginx-php-fpm docker image that is reference tries to remove the default nginx
config and replace it with it own config to point a different HTML root. If the
default nginx config is still present after the building the image, nginx will
start pointing to a different HTML root than the one set in the Dockerfile.
Currently the copy backend cannot handle removal of files from intermediate
layers. This can cause issues with docker images built using a Dockerfile
similar to the one listed here. Hence, we need to add REMOVE semantics to the
copy backend.
> Need to add REMOVE semantics to the copy backend
> ------------------------------------------------
>
> Key: MESOS-5277
> URL: https://issues.apache.org/jira/browse/MESOS-5277
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Environment: linux
> Reporter: Avinash Sridharan
> Assignee: Gilbert Song
> Labels: mesosphere
> Fix For: 0.29.0
>
>
> Some Dockerfiles run the `rm` command to remove files from the base image
> using the "RUN" directive in the Dockerfile. An example can be found here:
> https://github.com/ngineered/nginx-php-fpm.git
> In the final rootfs the removed files should not be present. Presence of
> these files in the final image can make the container misbehave. For example,
> the nginx-php-fpm docker image that is referenced tries to remove the default
> nginx config and replaces it with its own config to point to a different HTML
> root. If the default nginx config is still present after the building the
> image, nginx will start pointing to a different HTML root than the one set in
> the Dockerfile.
> Currently the copy backend cannot handle removal of files from intermediate
> layers. This can cause issues with docker images built using a Dockerfile
> similar to the one listed here. Hence, we need to add REMOVE semantics to the
> copy backend.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
