We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description
support buildah build --push.
i usually build image and run image for test many times, but i must run buildah push after buildah build.
buildah push
buildah build
is it possilbe let buildah directly push to remote registry after building an image, like dokcer build --push
dokcer build --push
buildah build -t docker.io/myrepo/myimage:v1.0 --push=true
Steps to reproduce the issue: 1. 2. 3.
Describe the results you received:
Describe the results you expected:
Output of rpm -q buildah or apt list buildah:
rpm -q buildah
apt list buildah
(paste your output here)
Output of buildah version:
buildah version
Output of podman version if reporting a podman build issue:
podman version
podman build
Output of cat /etc/*release:
cat /etc/*release
Output of uname -a:
uname -a
Output of cat /etc/containers/storage.conf:
cat /etc/containers/storage.conf
The text was updated successfully, but these errors were encountered:
Already being worked here: #4677
Sorry, something went wrong.
Duplicate of #4671
No branches or pull requests
Description
support buildah build --push.
i usually build image and run image for test many times, but i must run
buildah push
afterbuildah build
.is it possilbe let buildah directly push to remote registry after building an image, like
dokcer build --push
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Output of
rpm -q buildah
orapt list buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:The text was updated successfully, but these errors were encountered: