Unable to push to or pull images from the local registry. #934
Answered
by
stelahaveno
stelahaveno
asked this question in
Q&A
|
Answered by
stelahaveno
Dec 10, 2025
Replies: 4 comments 9 replies
|
@weiwei-cool Could you try container image pull --scheme http 192.168.2.5:5000/library/hello-world |
2 replies
|
Thank you! Unfortunately, that doesn’t work either. |
|
By the way, here is the relevant information about my local registry service: ➜ registry podman run -d --name registry -p 5000:5000 \
-v $PWD/config.yml:/etc/docker/registry/config.yml \
-v $PWD//var/lib/registry \
docker.io/library/registry:3.0.0➜ registry cat config.yml
version: 0.1
log:
level: info
storage:
filesystem:
rootdirectory: /var/lib/registry
http:
addr: :5000 |
|
Can you test with this? If you have DNS configured: container run --name registry -d --rm docker.io/library/registry:3
container image tag docker.io/library/registry:3 registry.test:5000/my-repository/registry:3
container image push --scheme http --platform linux/arm64 registry.test:5000/my-repository/registry:3 If not: container run --name registry -p 127.0.0.1:5001:5000 -d --rm docker.io/library/registry:3
container image tag docker.io/library/registry:3 localhost:5001/my-repository/registry:3
container image push --scheme http --platform linux/arm64 localhost:5001/my-repository/registry:3A couple of things to watch out for: macOS commonly makes use of port 5000. If you are going to use a port forwarder, you'll need to publish somewhere else. % lsof -i :5000
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ControlCe 765 jimbo 12u IPv4 0x166f87eeaf3795ed 0t0 TCP *:commplex-main (LISTEN)
ControlCe 765 jimbo 13u IPv6 0x76de30595a92dc42 0t0 TCP *:commplex-main (LISTEN)Until we sort out #913 you'll need to pay special attention to which platforms you push for an image, the error reporting for "I'm trying to push an image that supports more than one platform but the content for one of the platforms isn't present" isn't so hot. For images you build this shouldn't be a problem, because you're building the images and content, but for this example where I'm pushing the registry image that I ran, only the arm64 content is in the image store, so if I don't qualify that with the % container image push --scheme http localhost:5001/my-repository/registry:3
Error: notFound: "Content with digest sha256:f57ffd2bb01704b6082396158e77ca6d1112bc6fe32315c322864de804750d8a" |
7 replies
|
does |
|
|
Also, may I ask whether the issue I encountered can be reproduced on other computers? |
|
What do you see if you open your macOS Privacy & Security settings and open the Local Network tab? Do you see an entry for |
|
There’s only an option called container-runtime-linux, and it’s already enabled. |
|
I installed a fresh copy of macOS on an external hard drive, and everything works perfectly there—the issue cannot be reproduced. |
0 replies
|
The root cause of the issue is unknown, but completely reinstalling after clearing the container's data resolves the problem. |
0 replies
Answer selected by
stelahaveno
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The root cause of the issue is unknown, but completely reinstalling after clearing the container's data resolves the problem.