-
Notifications
You must be signed in to change notification settings - Fork 175
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
Containerfile.5.md should document "magic" build-args #1935
Comments
Interested in opening a PR? |
I must admit I'm tempted to, I'm simply afraid I may not be able to get to it soon-ish. I'll put it on my TODO list, but if anybody else is inspired to fix this they should go ahead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Podman and buildah (I believe) both support similar/same set of automatic build-args as in the Docker documentation (I'm guessing, so maybe not all are supported?):
TARGETPLATFORM
- platform of the build result. Eg linux/amd64, linux/arm/v7, windows/amd64.TARGETOS
- OS component of TARGETPLATFORMTARGETARCH
- architecture component of TARGETPLATFORMTARGETVARIANT
- variant component of TARGETPLATFORMBUILDPLATFORM
- platform of the node performing the build.BUILDOS
- OS component of BUILDPLATFORMBUILDARCH
- architecture component of BUILDPLATFORMBUILDVARIANT
- variant component of BUILDPLATFORMIn either case, some/all of these should be documented in the Containerfile man page. There are many situations where (esp) knowing (for example) the
BUILDARCH
is useful inRUN
commands. Importantly because it's golang-flavored and difficult to access elsewhere (i.e.uname -m
is different).The text was updated successfully, but these errors were encountered: