podman buildx build is missing `--push` flag
uhthomas opened this issue · 4 comments
uhthomas commented
Issue Description
I've just installed podman on Arch Linux with podman-docker and I'm unable to build an open source project because the buildx API is missing the --push
flag.
Error: unknown flag: --push
See 'podman buildx build --help'
I found containers/podman#17339, which was closed? The author claimed they would make another issue, but I can't find it if it exists.
Steps to reproduce the issue
Steps to reproduce the issue:
podman buildx build --push
Describe the results you received
Error: unknown flag: --push
See 'podman buildx build --help'
Describe the results you expected
A successful build and push.
podman info output
❯ podman info
host:
arch: amd64
buildahVersion: 1.31.2
cgroupControllers:
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: /usr/bin/conmon is owned by conmon 1:2.1.8-1
path: /usr/bin/conmon
version: 'conmon version 2.1.8, commit: 00e08f4a9ca5420de733bf542b930ad58e1a7e7d'
cpuUtilization:
idlePercent: 97.81
systemPercent: 0.44
userPercent: 1.75
cpus: 32
databaseBackend: boltdb
distribution:
distribution: arch
version: unknown
eventLogger: journald
freeLocks: 2046
hostname: paradise
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 6.5.5-zen1-1-zen
linkmode: dynamic
logDriver: journald
memFree: 17163735040
memTotal: 67345731584
networkBackend: netavark
networkBackendInfo:
backend: netavark
dns:
package: Unknown
package: /usr/lib/podman/netavark is owned by netavark 1.7.0-1
path: /usr/lib/podman/netavark
version: netavark 1.7.0
ociRuntime:
name: crun
package: /usr/bin/crun is owned by crun 1.9.2-1
path: /usr/bin/crun
version: |-
crun version 1.9.2
commit: 35274d346d2e9ffeacb22cc11590b0266a23d634
rundir: /run/user/1000/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
pasta:
executable: ""
package: ""
version: ""
remoteSocket:
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /etc/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: /usr/bin/slirp4netns is owned by slirp4netns 1.2.2-1
version: |-
slirp4netns version 1.2.2
commit: 0ee2d87523e906518d34a6b423271e4826f71faf
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.5.4
swapFree: 4294963200
swapTotal: 4294963200
uptime: 18h 40m 25.00s (Approximately 0.75 days)
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /home/thomas/.config/containers/storage.conf
containerStore:
number: 2
paused: 0
running: 0
stopped: 2
graphDriverName: overlay
graphOptions: {}
graphRoot: /home/thomas/.local/share/containers/storage
graphRootAllocated: 1967302877184
graphRootUsed: 444321849344
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 1
runRoot: /run/user/1000/containers
transientStore: false
volumePath: /home/thomas/.local/share/containers/storage/volumes
version:
APIVersion: 4.6.2
Built: 1693343961
BuiltTime: Tue Aug 29 22:19:21 2023
GitCommit: 5db42e86862ef42c59304c38aa583732fd80f178-dirty
GoVersion: go1.21.0
Os: linux
OsArch: linux/amd64
Version: 4.6.2
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
N/A
Additional information
N/A
rhatdan commented
@flouthoc I think we already have this issue, and I thought we came close to fixing it?
flouthoc commented
I'm closing this as duplicate.