Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
docker-tutorial
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Adam Lewenberg
docker-tutorial
Commits
612542ce
Commit
612542ce
authored
4 years ago
by
Adam Lewenberg
Browse files
Options
Downloads
Patches
Plain Diff
add TOC to practices page
parent
0d738420
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
practices/README.md
+6
-4
6 additions, 4 deletions
practices/README.md
with
6 additions
and
4 deletions
practices/README.md
+
6
−
4
View file @
612542ce
[[
_TOC_
]]
# Good Docker Practices
## Keep the Docker image simple (micro-services)
...
...
@@ -25,20 +27,20 @@ should work; people should think".
## When possible use container orchestration
Getting containers to interact and cooperate can be tricky, so use one of
container
tools like Kubernetes or Docker Compose to do this.
the orcestration
tools like Kubernetes or Docker Compose to do this.
## Use CI/CD (i.e., automation) to keep Docker images up-to-date
Set up automation to rebuild your Docker images periodically making sure
that you disable caching when building. This way you
will get the most
up-to-date and secure base
images for your
images.
that you disable caching when building. This way you
r image will have the
most
up-to-date and secure base images.
## Send diagnostic output to standard output
In the traditional server world we are used to sending logs to files. With
Docker containers it is usually better to send diagnostic output to
standard output. Kubernetes and other orchestration tools are designed
with the expectation that logging is sen
e
t to standard output.
with the expectation that logging is sent to standard output.
## Run containers in "read-only" mode
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment