-
Notifications
You must be signed in to change notification settings - Fork 758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci:docs] Add man page for Containerfile and .containerignore #3549
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
a322aaf
to
00cae3a
Compare
74c434f
to
d138c25
Compare
docs/Containerfile.5.md
Outdated
valid image. It is easy to start by pulling an image from the public | ||
repositories. | ||
|
||
-- **FROM** must be the first non-comment instruction in Containerfile. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-- **FROM** must be the first non-comment instruction in Containerfile. | |
-- **FROM** must be the first non-comment instruction in the Containerfile. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ARG is also permitted before the first FROM.
`FROM image@digest` | ||
|
||
-- The **FROM** instruction sets the base image for subsequent instructions. A | ||
valid Containerfile must have **FROM** as its first instruction. The image can be any |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
valid Containerfile must have **FROM** as its first instruction. The image can be any | |
valid Containerfile must have **FROM** as its first instruction. The image can be any |
An ARG
can be the first line too...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you going to adjust this?
difficult to update because it mixes with application-specific code. | ||
The solution is to use **ONBUILD** to register instructions in advance, to | ||
run later, during the next build stage. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are Arg and Onbuild not in alphanumeric order?
ARG user1 | ||
ARG buildno | ||
... | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just spotted a double lined comment here and other places. Are they correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is intentional, I believe. This Containerfile is based off of the original Dockerfile man page.
|
||
``` | ||
$ podman build --build-arg HTTPS_PROXY=https://my-proxy.example.com . | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I missed it, I didn't see a note that a second FROM in a Containerfile sets the values associated with an Arg variable to nil and they must be reset if they are to be used later in the Containerfile.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added this note to ARGS section.
Feb 2015, updated by Brian Goff (cpuguy83@gmail.com) for readability | ||
Sept 2015, updated by Sally O'Malley (somalley@redhat.com) | ||
Oct 2016, updated by Addam Hardy (addam.hardy@gmail.com) | ||
Aug 2021, converted Dockerfile man page to Containerfile by Dan Walsh (dwalsh@redhat.com) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be nice to have a Containers/Containerfiles repo with well documented Containerfiles for commona containers (nginx, onbuild examples, etc.). Not for the PR, just something we might want to consider.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That should be in Buildah if it was there.
docs/containerignore.5.md
Outdated
@@ -0,0 +1,87 @@ | |||
% "containerignore" "28" "Sep 2021" "" "Container User Manuals" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IDK, but can we rename this to .containerignore
or does that throw man pages for a loop?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure. Users are not going to type that though. I did setup a link to this from .containerignore
721c27b
to
5f2d8eb
Compare
@edsantiago PTAL I need help on hack/xref-helpmsgs-manpages |
5f2d8eb
to
9722a52
Compare
It's the add-a-test nagger: it doesn't have You can either add the magic no-new-tests string, or diff --git a/tests/validate/pr-should-include-tests b/tests/validate/pr-should-include-tests
index 4cc843df..6d2a1835 100755
--- a/tests/validate/pr-should-include-tests
+++ b/tests/validate/pr-should-include-tests
@@ -45,6 +45,7 @@ fi
filtered_changes=$(git diff --name-status $base $head |
awk '{print $2}' |
fgrep -vx .cirrus.yml |
+ fgrep -vx .gitignore |
fgrep -vx changelog.txt |
fgrep -vx go.mod |
fgrep -vx go.sum | |
9722a52
to
5bae6c9
Compare
At least one small nit that needs changing and I think you need to rebase anyway. One other question. |
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
ec3b666
to
a9e66ec
Compare
LGTM |
LGTM |
/lgtm |
Signed-off-by: Daniel J Walsh dwalsh@redhat.com
What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?