Closed jpopelka closed 3 years ago
Yeah, they should update that.
same thing here? https://github.com/redhat-actions/buildah-build/pull/47
Good thing we have the version output
same thing here? #47
Good thing we have the version output
Yes
Possible workaround as per buildah troubleshooting that we have did to solve this problem temporarily.
- run: |
sudo apt-get install fuse-overlayfs
mkdir -vp ~/.config/containers
printf "[storage.options]\nmount_program=\"/usr/bin/fuse-overlayfs\"" > ~/.config/containers/storage.conf
For anyone else coming into this issue, you can also work around this by using runs-on: ubuntu-18.04
for the job that runs buildah. So you'll get an older, working version of buildah while we look for a permanent solution.
Or you can use the workaround above
edit: does not sound like GitHub will fix this on their end, either. https://github.com/actions/virtual-environments/issues/3080
edit2: fixed in buildah-build@v2
this is fixed in v2 / v2.4 now.
if anyone is coming here because they see the warning printed on an ubuntu-18.04 system, don't worry, the action will still work.
however it is recommended to install fuse-overlayfs for better fs performance. upgrading to 20.04 will also remove the warning
Question
Hello, thank you for this action, it's marvelous. Today our builds started to fail and I'm wondering what's changed and where can be the cause.
The only difference between the failing one and 20hours old passing previous one I see in logs is the buildah version
1.19.8
(previous, OK) vs.1.20.0
(failed).I know it's most likely not your fault, that's why I'm creating a question in case someone else also hits this.