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 feature request related to a problem? Please describe.
Buildah version on Ubuntu 22.04 GitHub-hosted action runners is rather old (1.23.1 - from Ubuntu repositories), not supporting --cache-to. Even through mixing and matching packages from multiple Ubuntu releases, you can only get 1.28.2 - where registry cache still isn't working correctly.
Describe the solution you'd like
Would be nice if this action supported running buildah in a container (i.e. quay.io/buildah/stable image) transparently. With the ability to get the built image in "host" podman storage.
Describe alternatives you've considered
Just run the image using podman/docker. But then I completely lose the convenience of this action.
Run the entire workflow/job using buildah image. But I need the ubuntu-22.04 environment for other steps. Passing the image between jobs as a tar archive artifact would be slow and could probably hit GitHub limits.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Buildah version on Ubuntu 22.04 GitHub-hosted action runners is rather old (1.23.1 - from Ubuntu repositories), not supporting
--cache-to
. Even through mixing and matching packages from multiple Ubuntu releases, you can only get 1.28.2 - where registry cache still isn't working correctly.Describe the solution you'd like
Would be nice if this action supported running buildah in a container (i.e.
quay.io/buildah/stable
image) transparently. With the ability to get the built image in "host" podman storage.Describe alternatives you've considered
Just run the image using
podman
/docker
. But then I completely lose the convenience of this action.Run the entire workflow/job using buildah image. But I need the
ubuntu-22.04
environment for other steps. Passing the image between jobs as a tar archive artifact would be slow and could probably hit GitHub limits.Additional context
The text was updated successfully, but these errors were encountered: