-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
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
snapshoter.py error when running "buildah commit" on centos 8 #166
Comments
Same error appears when I try to build the container as user "root", therefore it seems like it is not related to rootless stuff. |
Does buildah function properly in that environment? Could you try |
So I did a quick test and it seems to work fine. If you need to see something different, let me know.
|
I looked a bit more in the issue with "buildah commit" and it seems ansible-bender ist missing a parameter. Following the test done above, I executed the following:
That gave me:
When I use the command like this, it works fine:
The intial error message from ansible-bender looks like this:
Therefore it seems like there is one parameter at the end missing (in the rhel/centos 8 version of buildah)? |
Thanks for such a thorough investigation! I recall I was playing with |
For the reference, the change happened in buildah 1.7.3: https://github.com/containers/buildah/releases/tag/v1.7.3 |
Fixes ansible-community#166 Signed-off-by: Tomas Tomecek <ttomecek@redhat.com>
Fixes ansible-community#166 Signed-off-by: Tomas Tomecek <ttomecek@redhat.com>
Fixes ansible-community#166 Signed-off-by: Tomas Tomecek <ttomecek@redhat.com>
Another thing which should be fixed here is that the build should fail once |
On centos 8 with python 3.6.8, buildah 1.5, ansible-bender (current head from master) and ansible 2.9.0rc2 as "vagrant" user, I get the following error when I try to build a container with ansble-bender build simple-playbook.yaml:
It's worth to mention that even though there is an error, the image gets written. If I try to run a playbook with multiple tasks, it seems like all the other tasks are skipped due to the error.
The text was updated successfully, but these errors were encountered: