How to persist application configuration files and content in Docker container
I am new to Docker and am creating a multi-container application using a docker-compose file that includes a Postgres database and a Django/Wagtail application. I understand the concept of backup/restore the data written to the database in volume.
But, I am having trouble grasping the options for how to preserve content like static files, app config files.Simply put, once I run my initial docker container and change DB models, make migrations and create templates(for example)-- How can I make make this content available so that one can run an newly created image of the app that reflects the current state? Should I be using COPY or ADD in the dockerfile, or reference a volume for these files in docker-compose.yml? Here is the docker-compose.yml and dockerfile that is the starting point taken from a Dockerhub image and corresponding Github build instructions. https://github.com/fffunction/setting-up-wagtail-with-docker
dockerfile
FROM python:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY requirements.txt /usr/src/app/
RUN pip install --no-cache-dir -r requirements.txt
ENV PYTHONUNBUFFERED 1
ENV PYTHONDONTWRITEBYTECODE 1
ENV LANG en_US.UTF-8
ENV PYTHONIOENCODING utf_8
docker-compose.yml
web:
build: .
dockerfile: .dockerfile
command: python manage.py runserver 0.0.0.0:80
volumes:
- ./:/usr/src/app
links:
- postgres
- elasticsearch
ports:
- "80:80"
environment:
- DEBUG=True
- DEV=True
- DATABASE_URL=postgres://postgres:@postgres:5432/postgres
- ELASTICSEARCH_URL=http://elasticsearch:9200
- SECRET_KEY=notasecretreplaceme
postgres:
image: postgres
ports:
- "5432:5432"
elasticsearch:
image: orchardup/elasticsearch
ports:
- "9200:9200"
docker docker-compose dockerfile
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
add a comment |
I am new to Docker and am creating a multi-container application using a docker-compose file that includes a Postgres database and a Django/Wagtail application. I understand the concept of backup/restore the data written to the database in volume.
But, I am having trouble grasping the options for how to preserve content like static files, app config files.Simply put, once I run my initial docker container and change DB models, make migrations and create templates(for example)-- How can I make make this content available so that one can run an newly created image of the app that reflects the current state? Should I be using COPY or ADD in the dockerfile, or reference a volume for these files in docker-compose.yml? Here is the docker-compose.yml and dockerfile that is the starting point taken from a Dockerhub image and corresponding Github build instructions. https://github.com/fffunction/setting-up-wagtail-with-docker
dockerfile
FROM python:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY requirements.txt /usr/src/app/
RUN pip install --no-cache-dir -r requirements.txt
ENV PYTHONUNBUFFERED 1
ENV PYTHONDONTWRITEBYTECODE 1
ENV LANG en_US.UTF-8
ENV PYTHONIOENCODING utf_8
docker-compose.yml
web:
build: .
dockerfile: .dockerfile
command: python manage.py runserver 0.0.0.0:80
volumes:
- ./:/usr/src/app
links:
- postgres
- elasticsearch
ports:
- "80:80"
environment:
- DEBUG=True
- DEV=True
- DATABASE_URL=postgres://postgres:@postgres:5432/postgres
- ELASTICSEARCH_URL=http://elasticsearch:9200
- SECRET_KEY=notasecretreplaceme
postgres:
image: postgres
ports:
- "5432:5432"
elasticsearch:
image: orchardup/elasticsearch
ports:
- "9200:9200"
docker docker-compose dockerfile
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
Perhaps this question is too broad and needs more clarity. When I run docker-compose build , app files are created on the host machine filesystem, I think I want them created on the container's filesystem so that they would persist if I create an image of the current state of the app to deploy elsewhere.
– JohnnyP
Nov 24 '18 at 17:50
add a comment |
I am new to Docker and am creating a multi-container application using a docker-compose file that includes a Postgres database and a Django/Wagtail application. I understand the concept of backup/restore the data written to the database in volume.
But, I am having trouble grasping the options for how to preserve content like static files, app config files.Simply put, once I run my initial docker container and change DB models, make migrations and create templates(for example)-- How can I make make this content available so that one can run an newly created image of the app that reflects the current state? Should I be using COPY or ADD in the dockerfile, or reference a volume for these files in docker-compose.yml? Here is the docker-compose.yml and dockerfile that is the starting point taken from a Dockerhub image and corresponding Github build instructions. https://github.com/fffunction/setting-up-wagtail-with-docker
dockerfile
FROM python:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY requirements.txt /usr/src/app/
RUN pip install --no-cache-dir -r requirements.txt
ENV PYTHONUNBUFFERED 1
ENV PYTHONDONTWRITEBYTECODE 1
ENV LANG en_US.UTF-8
ENV PYTHONIOENCODING utf_8
docker-compose.yml
web:
build: .
dockerfile: .dockerfile
command: python manage.py runserver 0.0.0.0:80
volumes:
- ./:/usr/src/app
links:
- postgres
- elasticsearch
ports:
- "80:80"
environment:
- DEBUG=True
- DEV=True
- DATABASE_URL=postgres://postgres:@postgres:5432/postgres
- ELASTICSEARCH_URL=http://elasticsearch:9200
- SECRET_KEY=notasecretreplaceme
postgres:
image: postgres
ports:
- "5432:5432"
elasticsearch:
image: orchardup/elasticsearch
ports:
- "9200:9200"
docker docker-compose dockerfile
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
I am new to Docker and am creating a multi-container application using a docker-compose file that includes a Postgres database and a Django/Wagtail application. I understand the concept of backup/restore the data written to the database in volume.
But, I am having trouble grasping the options for how to preserve content like static files, app config files.Simply put, once I run my initial docker container and change DB models, make migrations and create templates(for example)-- How can I make make this content available so that one can run an newly created image of the app that reflects the current state? Should I be using COPY or ADD in the dockerfile, or reference a volume for these files in docker-compose.yml? Here is the docker-compose.yml and dockerfile that is the starting point taken from a Dockerhub image and corresponding Github build instructions. https://github.com/fffunction/setting-up-wagtail-with-docker
dockerfile
FROM python:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY requirements.txt /usr/src/app/
RUN pip install --no-cache-dir -r requirements.txt
ENV PYTHONUNBUFFERED 1
ENV PYTHONDONTWRITEBYTECODE 1
ENV LANG en_US.UTF-8
ENV PYTHONIOENCODING utf_8
docker-compose.yml
web:
build: .
dockerfile: .dockerfile
command: python manage.py runserver 0.0.0.0:80
volumes:
- ./:/usr/src/app
links:
- postgres
- elasticsearch
ports:
- "80:80"
environment:
- DEBUG=True
- DEV=True
- DATABASE_URL=postgres://postgres:@postgres:5432/postgres
- ELASTICSEARCH_URL=http://elasticsearch:9200
- SECRET_KEY=notasecretreplaceme
postgres:
image: postgres
ports:
- "5432:5432"
elasticsearch:
image: orchardup/elasticsearch
ports:
- "9200:9200"
docker docker-compose dockerfile
docker docker-compose dockerfile
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
edited Nov 24 '18 at 2:39
JohnnyP
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
asked Nov 24 '18 at 2:32
JohnnyPJohnnyP
11517
11517
Perhaps this question is too broad and needs more clarity. When I run docker-compose build , app files are created on the host machine filesystem, I think I want them created on the container's filesystem so that they would persist if I create an image of the current state of the app to deploy elsewhere.
– JohnnyP
Nov 24 '18 at 17:50
add a comment |
Perhaps this question is too broad and needs more clarity. When I run docker-compose build , app files are created on the host machine filesystem, I think I want them created on the container's filesystem so that they would persist if I create an image of the current state of the app to deploy elsewhere.
– JohnnyP
Nov 24 '18 at 17:50
Perhaps this question is too broad and needs more clarity. When I run docker-compose build , app files are created on the host machine filesystem, I think I want them created on the container's filesystem so that they would persist if I create an image of the current state of the app to deploy elsewhere.
– JohnnyP
Nov 24 '18 at 17:50
Perhaps this question is too broad and needs more clarity. When I run docker-compose build , app files are created on the host machine filesystem, I think I want them created on the container's filesystem so that they would persist if I create an image of the current state of the app to deploy elsewhere.
– JohnnyP
Nov 24 '18 at 17:50
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%2f53454698%2fhow-to-persist-application-configuration-files-and-content-in-docker-container%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%2f53454698%2fhow-to-persist-application-configuration-files-and-content-in-docker-container%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
Perhaps this question is too broad and needs more clarity. When I run docker-compose build , app files are created on the host machine filesystem, I think I want them created on the container's filesystem so that they would persist if I create an image of the current state of the app to deploy elsewhere.
– JohnnyP
Nov 24 '18 at 17:50