shouldn't the current directory be the default context for "podman build"?
"man podman-build" suggests that the context argument is optional: SYNOPSIS podman build [options] [context] podman image build [options] [context] ... If no context directory is specified, then Podman will assume the current working directory as the build context, which should contain the Containerfile. but if i have a directory with nothing but a Containerfile, i get: $ podman build Error: no context directory specified, and no containerfile specified $ OTOH, specifying context of current directory: $ podman build . STEP 1: FROM alpine:latest ... etc etc ... thoughts? rday
The `podman build` without a dot or other context directory should be working as of Podman v1.6.2 and later. Can you check your version please? If it's the latest and greatest version, please spin up an issue against Buildah which handles the build work for Podman at: https://github.com/containers/buildah/issues t On Sun, Dec 29, 2019 at 10:58 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
"man podman-build" suggests that the context argument is optional:
SYNOPSIS podman build [options] [context] podman image build [options] [context]
...
If no context directory is specified, then Podman will assume the current working directory as the build context, which should contain the Containerfile.
but if i have a directory with nothing but a Containerfile, i get:
$ podman build Error: no context directory specified, and no containerfile specified $
OTOH, specifying context of current directory:
$ podman build . STEP 1: FROM alpine:latest ... etc etc ...
thoughts?
rday _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
On Sun, 29 Dec 2019, Tom & Susie Sweeney wrote:
The `podman build` without a dot or other context directory should be working as of Podman v1.6.2 and later. Can you check your version please? If it's the latest and greatest version, please spin up an issue against Buildah which handles the build work for Podman at: https://github.com/containers/buildah/issues
current fully-updated fedora 31: $ podman --version podman version 1.6.2 will file issue. rday
hi need -f docerfile exsample podman build -f Containerfile -t alpmap:1.0
If you're using the Containerfile or the Dockerfile in the current directory, you should need the to use the `-f` option. If you did `podman build -t alpmap:1.0 .` it should work for you. I just tried `podman build -f Containerfile -t test .` and it worked for me. I may have missed it, but did you include a period (`.`) at the end of the command to specify the context directory? That might be the hiccup. t On 12/12/24 11:45 AM, iseymur@gmail.com wrote:
hi need -f docerfile exsample podman build -f Containerfile -t alpmap:1.0 _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
UGH! Typo in my reply. In the first sentence I was missing the word NOT! `If you're using the Containerfile or the Dockerfile in the current directory, you should *NOT* need the to use the `-f` option. If you did `podman build -t alpmap:1.0 .` it should work for you.` t On 12/12/24 11:45 AM, iseymur@gmail.com wrote:
hi need -f docerfile exsample podman build -f Containerfile -t alpmap:1.0 _______________________________________________ Podman mailing list --podman@lists.podman.io To unsubscribe send an email topodman-leave@lists.podman.io
participants (4)
-
iseymur＠gmail.com -
Robert P. J. Day -
Tom & Susie Sweeney -
Tom Sweeney