Mixing
Docker: share data between containers in non-persistent way to allow for code upgrade
In a php-fpm and nginx container setup the source code usually needs to be available to both containers. In my case I'd like to dockerize Magento. In Magento the nginx is configured in such a way that it looks for the existence of files before it commits the request to the php engine.
According to the best practices from Docker for an production environment I copied the source code into the php container during the build process. My first idea to share the source code with the nginx container was to use a named volume that is mounted to the root of both containers. However, the data in named volumes persist even after editing the source code and rebuilding the php container. This comes in handy for dynamic content like file uploads etc. but how do I upgrade the source code? Should I delete the volume everytime the source code is changed? How do I persist dynamic content in this case?
In a nutshell:
- I'd like to have non-persistent volume to share source code between php and nginx
- A persistent volume (but still shared with nginx) for folders with dynamic content (e.g. file uploads)
For Magento that would be:
- Non-persistent volume for files and folders like
./index.php,./vendor/,./app/(except./app/etc/env.phpand./app/etc/config.phpsince that are configuration files), etc. - Persistent volume for files and folders like
./pub/media/,./app/etc/env.php,./app/etc/config.php, etc.
php docker nginx docker-compose docker-volume
asked Nov 22 '18 at 9:06
SoerenSoeren
112
add a comment |
In a php-fpm and nginx container setup the source code usually needs to be available to both containers. In my case I'd like to dockerize Magento. In Magento the nginx is configured in such a way that it looks for the existence of files before it commits the request to the php engine.
According to the best practices from Docker for an production environment I copied the source code into the php container during the build process. My first idea to share the source code with the nginx container was to use a named volume that is mounted to the root of both containers. However, the data in named volumes persist even after editing the source code and rebuilding the php container. This comes in handy for dynamic content like file uploads etc. but how do I upgrade the source code? Should I delete the volume everytime the source code is changed? How do I persist dynamic content in this case?
In a nutshell:
- I'd like to have non-persistent volume to share source code between php and nginx
- A persistent volume (but still shared with nginx) for folders with dynamic content (e.g. file uploads)
For Magento that would be:
- Non-persistent volume for files and folders like
./index.php,./vendor/,./app/(except./app/etc/env.phpand./app/etc/config.phpsince that are configuration files), etc. - Persistent volume for files and folders like
./pub/media/,./app/etc/env.php,./app/etc/config.php, etc.
php docker nginx docker-compose docker-volume
asked Nov 22 '18 at 9:06
SoerenSoeren
112
any updates? :) Did you solve this?
– pic0
Feb 20 at 18:42
1
Somewhat: for production I copy the source code into each container and only share uploaded files etc., but the problem still persists in the development stage. For now I remove the named volume in the case that the source code of the framework changes. Here is what I came up with: github.com/zsoerenm/…
– Soeren
Feb 21 at 19:14
add a comment |
In a php-fpm and nginx container setup the source code usually needs to be available to both containers. In my case I'd like to dockerize Magento. In Magento the nginx is configured in such a way that it looks for the existence of files before it commits the request to the php engine.
According to the best practices from Docker for an production environment I copied the source code into the php container during the build process. My first idea to share the source code with the nginx container was to use a named volume that is mounted to the root of both containers. However, the data in named volumes persist even after editing the source code and rebuilding the php container. This comes in handy for dynamic content like file uploads etc. but how do I upgrade the source code? Should I delete the volume everytime the source code is changed? How do I persist dynamic content in this case?
In a nutshell:
- I'd like to have non-persistent volume to share source code between php and nginx
- A persistent volume (but still shared with nginx) for folders with dynamic content (e.g. file uploads)
For Magento that would be:
- Non-persistent volume for files and folders like
./index.php,./vendor/,./app/(except./app/etc/env.phpand./app/etc/config.phpsince that are configuration files), etc. - Persistent volume for files and folders like
./pub/media/,./app/etc/env.php,./app/etc/config.php, etc.
php docker nginx docker-compose docker-volume
asked Nov 22 '18 at 9:06
SoerenSoeren
112
In a php-fpm and nginx container setup the source code usually needs to be available to both containers. In my case I'd like to dockerize Magento. In Magento the nginx is configured in such a way that it looks for the existence of files before it commits the request to the php engine.
According to the best practices from Docker for an production environment I copied the source code into the php container during the build process. My first idea to share the source code with the nginx container was to use a named volume that is mounted to the root of both containers. However, the data in named volumes persist even after editing the source code and rebuilding the php container. This comes in handy for dynamic content like file uploads etc. but how do I upgrade the source code? Should I delete the volume everytime the source code is changed? How do I persist dynamic content in this case?
In a nutshell:
- I'd like to have non-persistent volume to share source code between php and nginx
- A persistent volume (but still shared with nginx) for folders with dynamic content (e.g. file uploads)
For Magento that would be:
- Non-persistent volume for files and folders like
./index.php,./vendor/,./app/(except./app/etc/env.phpand./app/etc/config.phpsince that are configuration files), etc. - Persistent volume for files and folders like
./pub/media/,./app/etc/env.php,./app/etc/config.php, etc.
php docker nginx docker-compose docker-volume
php docker nginx docker-compose docker-volume
asked Nov 22 '18 at 9:06
SoerenSoeren
112
asked Nov 22 '18 at 9:06
SoerenSoeren
112
edited Nov 22 '18 at 9:11
Soeren
asked Nov 22 '18 at 9:06
SoerenSoeren
112
asked Nov 22 '18 at 9:06
SoerenSoeren
112
asked Nov 22 '18 at 9:06
SoerenSoeren
112
112
any updates? :) Did you solve this?
– pic0
Feb 20 at 18:42
1
Somewhat: for production I copy the source code into each container and only share uploaded files etc., but the problem still persists in the development stage. For now I remove the named volume in the case that the source code of the framework changes. Here is what I came up with: github.com/zsoerenm/…
– Soeren
Feb 21 at 19:14
add a comment |
any updates? :) Did you solve this?
– pic0
Feb 20 at 18:42
1
Somewhat: for production I copy the source code into each container and only share uploaded files etc., but the problem still persists in the development stage. For now I remove the named volume in the case that the source code of the framework changes. Here is what I came up with: github.com/zsoerenm/…
– Soeren
Feb 21 at 19:14
any updates? :) Did you solve this?
– pic0
Feb 20 at 18:42
any updates? :) Did you solve this?
– pic0
Feb 20 at 18:42
1
1
Somewhat: for production I copy the source code into each container and only share uploaded files etc., but the problem still persists in the development stage. For now I remove the named volume in the case that the source code of the framework changes. Here is what I came up with: github.com/zsoerenm/…
– Soeren
Feb 21 at 19:14
Somewhat: for production I copy the source code into each container and only share uploaded files etc., but the problem still persists in the development stage. For now I remove the named volume in the case that the source code of the framework changes. Here is what I came up with: github.com/zsoerenm/…
– Soeren
Feb 21 at 19:14
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427259%2fdocker-share-data-between-containers-in-non-persistent-way-to-allow-for-code-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427259%2fdocker-share-data-between-containers-in-non-persistent-way-to-allow-for-code-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
any updates? :) Did you solve this?
– pic0
Feb 20 at 18:42
1
Somewhat: for production I copy the source code into each container and only share uploaded files etc., but the problem still persists in the development stage. For now I remove the named volume in the case that the source code of the framework changes. Here is what I came up with: github.com/zsoerenm/…
– Soeren
Feb 21 at 19:14