You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe
While I was testing extension installation and needed to build image then push it to the registry. It was very annoying to switching between 'Build Image' and 'Images' page:
Build page does not remember anything and I have to go and fill Containerfile and full image name registry/repo/name
Pushing the image after build requires to go to 'Images' page and push specific tag for the image
Pushing image asks to select the image tag, but I already requested to push specific tag in 'Images' page and it adds additional click
If there is a problem with image, I would need to rebuild and start from step (1)
After that I switched to terminal running single command
podman build . && podman push
Describe the solution you'd like
It would be good if I can push the image after build without leaving the 'Build Image' page:
Additional button next to 'Build' and 'Done'
Switch 'Push image after build' in the build form
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
About one remark I think it has been discussed a while ago that build should provide also history / or a kind of 'build context' being remembered so if you need to build again an image you have a way to go back
Is your enhancement related to a problem? Please describe
While I was testing extension installation and needed to build image then push it to the registry. It was very annoying to switching between 'Build Image' and 'Images' page:
After that I switched to terminal running single command
Describe the solution you'd like
It would be good if I can push the image after build without leaving the 'Build Image' page:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: