Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG] New version breaks simple build #50

Closed
gfvirga opened this issue Apr 2, 2021 · 2 comments
Closed

[BUG] New version breaks simple build #50

gfvirga opened this issue Apr 2, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@gfvirga
Copy link

gfvirga commented Apr 2, 2021

Version

Run redhat-actions/buildah-build@v2
/usr/bin/buildah version
Version: 1.20.0
Go Version: go1.15.2
Image Spec: 1.0.1-dev
Runtime Spec: 1.0.2-dev
CNI Spec: 0.4.0
libcni Version:
image Version: 5.10.5

Describe the bug

Hello,
After the upgrade to 1.20.0 I can't build a simple python.
It seems that docker.io has been removed from the registry.conf and some permission issue is happening

Working build - https://github.com/gfvirga/http-liveness/runs/2242528975?check_suite_focus=true
Can't find python - https://github.com/gfvirga/http-liveness/runs/2250342456?check_suite_focus=true
Tar error - https://github.com/gfvirga/http-liveness/runs/2250371480?check_suite_focus=true

I am using the default agent from github.

Steps to reproduce, workflow links, screenshots

Run redhat-actions/buildah-build@v2
/usr/bin/buildah version
Version:         1.20.0
Go Version:      go1.15.2
Image Spec:      1.0.1-dev
Runtime Spec:    1.0.2-dev
CNI Spec:        0.4.0
libcni Version:  
image Version:   5.10.5
Git Commit:      
Built:           Thu Jan  1 00:00:00 1970
OS/Arch:         linux/amd64
Performing build from Dockerfile
/usr/bin/buildah bud --arch amd64 -f /home/runner/work/http-liveness/http-liveness/Dockerfile --format docker -t gfvirga/httpliveness:latest /home/runner/work/http-liveness/http-liveness
STEP 1: FROM python
Resolving "python" using unqualified-search registries (/etc/containers/registries.conf)
Getting image source signatures
Copying blob sha256:234b70d0479d7f16d7ee8d04e4ffdacc57d7d14313faf59d332f18b2e9418743
Copying blob sha256:04a31b4508b8e95fb3cb25486c4068185054895b12e0611e386a002ee9c0e07c
Copying blob sha256:6fa07a00e2f029c4b2c7f177a2b696f1b3510040cde4f5bb06ddbca98e7fbf76
Copying blob sha256:5d6f1e8117dbb1c6a57603cb4f321a861a08105a81bcc6b01b0ec2b78c8523a5
Copying blob sha256:004f1eed87df3f75f5e2a1a649fa7edd7f713d1300532fd0909bb39cd48437d7
Copying blob sha256:48c2faf66abec3dce9f54d6722ff592fce6dd4fb58a0d0b72282936c6598a3b3
Copying blob sha256:2eee1b8e253830859988454f07e1e98387cf5e3730e7eedee333aa7fd1a04be2
Copying blob sha256:1823d93d969893b61303752fa11b710c4befae6f15a775fad2c2c0bcb619cf2e
Copying blob sha256:b48672c0140e5d73a8b044e4c1c229f3cc88fd8ff645c7fc6f774c830ae1f8d4
Copying config sha256:587b1bc803b36f65923fe677467bb619b4e464d7f988377bb5c6c0a26eef044d
Writing manifest to image destination
Storing signatures
error creating build container: 2 errors occurred while pulling:
 * Error committing the finished image: error adding layer with blob "sha256:5d6f1e8117dbb1c6a57603cb4f321a861a08105a81bcc6b01b0ec2b78c8523a5": Error processing tar file(exit status 1): operation not permitted
 * Error initializing source docker://quay.io/python:latest: Error reading manifest latest in quay.io/python: StatusCode: 404, <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final/...
level=error msg="exit status 125"
Error: Error: buildah exited with code 125
Resolving "python" using unqualified-search registries (/etc/containers/registries.conf)
Getting image source signatures
Copying blob sha256:234b70d0479d7f16d7ee8d04e4ffdacc57d7d14313faf59d332f18b2e9418743
Copying blob sha256:04a31b4508b8e95fb3cb25486c4068185054895b12e0611e386a002ee9c0e07c
Copying blob sha256:6fa07a00e2f029c4b2c7f177a2b696f1b3510040cde4f5bb06ddbca98e7fbf76
Copying blob sha256:5d6f1e8117dbb1c6a57603cb4f321a861a08105a81bcc6b01b0ec2b78c8523a5
Copying blob sha256:004f1eed87df3f75f5e2a1a649fa7edd7f713d1300532fd0909bb39cd48437d7
Copying blob sha256:48c2faf66abec3dce9f54d6722ff592fce6dd4fb58a0d0b72282936c6598a3b3
Copying blob sha256:2eee1b8e253830859988454f07e1e98387cf5e3730e7eedee333aa7fd1a04be2
Copying blob sha256:1823d93d969893b61303752fa11b710c4befae6f15a775fad2c2c0bcb619cf2e
Copying blob sha256:b48672c0140e5d73a8b044e4c1c229f3cc88fd8ff645c7fc6f774c830ae1f8d4
Copying config sha256:587b1bc803b36f65923fe677467bb619b4e464d7f988377bb5c6c0a26eef044d
Writing manifest to image destination
Storing signatures
error creating build container: 2 errors occurred while pulling:
 * Error committing the finished image: error adding layer with blob "sha256:5d6f1e8117dbb1c6a57603cb4f321a861a08105a81bcc6b01b0ec2b78c8523a5": Error processing tar file(exit status 1): operation not permitted
 * Error initializing source docker://quay.io/python:latest: Error reading manifest latest in quay.io/python: StatusCode: 404, <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final/...
level=error msg="exit status 125"
@gfvirga gfvirga added the bug Something isn't working label Apr 2, 2021
@tetchel
Copy link
Contributor

tetchel commented Apr 2, 2021 •
edited
Loading

I'm not sure about the "error reading manifest" but the first error is #45, there's a workaround there while we see if buildah will provide a more complete fix.

Add that workaround and we'll see if that fixes the second error too

@gfvirga
Copy link
Author

gfvirga commented Apr 2, 2021

That worked! Thanks

@gfvirga gfvirga closed this as completed Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gfvirga @tetchel