This repository has been archived by the owner on Oct 19, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 83
Config overrides disappear when using a docker volume #419
Comments
jaitaiwan
pushed a commit
to jaitaiwan/php-docker
that referenced
this issue
Feb 14, 2018
When config files are inside a docker volume used as the document root it will cause any config files that move-config-files.sh moves to effectively disappear from the docker volume which is unintended behaviour. Fixes GoogleCloudPlatform#419
jaitaiwan
pushed a commit
to jaitaiwan/php-docker
that referenced
this issue
Feb 14, 2018
When config files are inside a docker volume used as the document root it will cause any config files that move-config-files.sh moves to effectively disappear from the docker volume which is unintended behaviour. Fixes GoogleCloudPlatform#419
frost-byte
pushed a commit
to Wiser-Owl/php-docker
that referenced
this issue
May 9, 2021
* Allow building deprecated mongo from pecl The mongo pecl extension is needed for phalcon as the object document mapper provided by phalcon works exclusively with the deprecated library * Use the correct copyright for mongo pecl * Use cp instead of mv for config files When config files are inside a docker volume used as the document root it will cause any config files that move-config-files.sh moves to effectively disappear from the docker volume which is unintended behaviour. Fixes GoogleCloudPlatform#419 * Normalise copyright and version req Updated the copyright to remove the full licence message and ensure building only for php 5.6
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using a docker volume with
SKIP_LOCKDOWN_DOCUMENT_ROOT
(and potentially without it), any config files that are moved byphp-base/build-scripts/move-config-files.sh
are surprisingly moved from the volume to inside the image.So I'll be adding to my PR to change all
mv
commands tocp
commands so they don't disappear.The text was updated successfully, but these errors were encountered: