This repository was archived by the owner on May 21, 2021. It is now read-only.
forked from RHsyseng/sturdy-chainsaw
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathhelp.md.generic
More file actions
40 lines (27 loc) · 1.26 KB
/
help.md.generic
File metadata and controls
40 lines (27 loc) · 1.26 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
% IMAGE_NAME(1)
% MAINTAINER
% DATE
# DESCRIPTION
Describe in greater detail the role or purpose of the image. This can include more specifics about the
packages that make up the image. You can also describe whether image is meant to be interactive
or more service oriented.
# USAGE
Describe how to run the image as a container and what factors might influence the behaviour of the image
itself. For example:
To set up the host system for use by the XYZ container, run:
atomic install XYZimage
To run the XYZ container (after it is installed), run:
atomic run XYZimage
To remove the XYZ container (not the image) from your system, run:
atomic uninstall XYZimage
To upgrade the XYZ container from your system, run:
atomic upgrade XYZimage
# LABELS
Describe LABEL settings (from the Dockerfile that created the image) that contains pertinent information.
For containers run by atomic, that could include INSTALL, RUN, UNINSTALL, and UPDATE LABELS. Others could
include BZComponent, Name, Version, Release, and Architecture.
# SECURITY IMPLICATIONS
If you expose ports or run with privileges, it would be warranted to briefly note those and provide
an explanation if needed.
# HISTORY
Similar to a Changelog of sorts which can be as detailed as the maintainer wishes.