-
Notifications
You must be signed in to change notification settings - Fork 787
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
building image with sha id in FROM #2836
Comments
@nalind @TomSweeneyRedHat PTAL |
In this case the hex part of I think fixing this in buildah is as easy as recognizing that form and internally stripping off the I wasn't able to reproduce the error using a spot check with imagebuilder from its master branch. I'd pulled the image manually before that, though, since an image ID by itself isn't enough information for either docker or podman to be able to pull it from a registry. Were you testing with a different version? |
I have imagebuilder-0.0.6-1.el7eng.x86_64 but this issues seems to be problem with underlying podman, |
Ah, so you're pointing imagebuilder at podman? That's an important detail, but it suggests that imagebuilder is correctly passing the name from the Dockerfile to the build API endpoint, so we're really just talking about podman. |
I've modified description (removed those docker/imagebuilder builds), this should be issue only about buildah build with podman |
Since this is really a Buildah bug, I will move to Buildah, once fixed, there we can revendor into Podman |
ok |
@vrothberg can you take a look at this one if you've a spare moment or three please? |
Detect local-image lookups by digest. Those clearly refer to local images only, so we must not proceed to remote lookups. Fixes: containers#2836 Signed-off-by: Valentin Rothberg <[email protected]>
Detect local-image lookups by digest. Those clearly refer to local images only, so we must not proceed to remote lookups. Note that the specifed digest refers to an image ID and not to the digest of an image's manifest. Fixes: containers#2836 Signed-off-by: Valentin Rothberg <[email protected]>
Detect local-image lookups by digest. Those clearly refer to local images only, so we must not proceed to remote lookups. Note that the specifed digest refers to an image ID and not to the digest of an image's manifest. Fixes: containers#2836 Signed-off-by: Valentin Rothberg <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
when building image with buildah with podman
and having in FROM sha of local image ID,
build fails
Steps to reproduce the issue:
create simple Dockerfile when in FROM you will specify sha of local image ID
build image : buildah bud
build will fail
$ buildah bud -t test ./
STEP 1: FROM sha256:33df2983b06100d70b79fc667656a61bf2ca3978ff976a3db42de36f9b11192e
error creating build container: The following failures happened while trying to pull image specified by "sha256:33df2983b06100d70b79fc667656a61bf2ca3978ff976a3db42de36f9b11192e" based on search registries in /etc/containers/registries.conf:
denied: requested access to the resource is denied
unauthorized: authentication required
Describe the results you received:
build fails
Describe the results you expected:
having in FROM sha of local image ID is working with docker (docker/imagebuilder build with docker)
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
No
Additional environment details (AWS, VirtualBox, physical, etc.):
physical with virtenv
The text was updated successfully, but these errors were encountered: