Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
C
configuration
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
OpenEdx
configuration
Commits
560d20a7
Commit
560d20a7
authored
Jan 13, 2016
by
Calen Pennington
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify some docker conventions
parent
15dceca5
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
0 deletions
+16
-0
docker/README.md
+16
-0
No files found.
docker/README.md
View file @
560d20a7
...
...
@@ -21,6 +21,10 @@ using a set of make commands.
```
shell
make docker.build.<service>
# Build the service container (but don't tag it)
# By convention, this will build the container using
# the currently checked-out configuration repository,
# and will build on top of the most-recently available
# base container image from dockerhub.
make docker.test.<service>
# Test that the Dockerfile for <service> will build.
# This will rebuild any edx-specific containers that
...
...
@@ -33,3 +37,15 @@ make docker.pkg.<service> # Package <service> for publishing to Dockerhub. Th
make docker.push.<service>
# Push <service> to Dockerhub as latest.
```
## Conventions
In order to facilitate development, Dockerfiles should be based on
one of the
`edxops/<ubuntu version>-common`
base images, and should
`COPY . /edx/app/edx_ansible/edx_ansible`
in order to load your local
ansible plays into the image. The actual work of configuring the image
should be done by executing ansible (rather than explicit steps in the
Dockerfile), unless those steps are docker specific. Devstack-specific
steps can be tagged with the
`devstack:install`
tag in order that they
only run when building a devstack image.
The user used in the
`Dockerfile`
should be
`root`
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment