Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1684295 - podman build . -t spec fails, but works for docker
Summary: podman build . -t spec fails, but works for docker
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: podman
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-28 22:15 UTC by Eric Paris
Modified: 2019-03-01 13:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Paris 2019-02-28 22:15:24 UTC
docker build . -t quay.io/eparis/ssh

works fine.

podman build . -t quay.io/eparis/ssh

results in an image being built, but not tagged.

podman build -t quay.io/eparis/ssh .

works just fine.

Comment 2 Daniel Walsh 2019-02-28 22:23:17 UTC
We require all options to be processes before arguments.

Comment 3 Matthew Heon 2019-02-28 22:25:36 UTC
Buildah explicitly disables adding arguments after the dockerfile path in 'buildah bud'. Podman build does not, instead building but not tagging as described here. Possibly an artifact of the Cobra migration?

Comment 4 Daniel Walsh 2019-03-01 09:48:46 UTC
I am not sure if this is a cobra thing.   I new we had problems with urfave before.

Commands like 
buildah run
podman exec
podman run

All have to have this requirement as well.  So we just forced it on all commands, as I recall.

Comment 5 Daniel Walsh 2019-03-01 13:20:54 UTC
It seems like just setting

+       flags.SetInterspersed(true)

Fixes this?


Note You need to log in before you can comment on or make changes to this bug.