Unable to push container images to Nexus from host, connected via VPN

[abhaybhegde]

Hi,

Our organization uses Nexus to host container images. I am connected to our corporate VPN and trying to push container image to our Nexus from Windows command line. Below is what i am trying:

podman push nexus-repo: app-name: tag

Initially i get the below messages
Getting image source signatures
Copying blob sha256:7f28618cff614f15f4db079284b1d5b7dbc9a4e45803451907438046ab9b1255
Copying blob sha256:7be286359f7f1b9f82d56d843c2109897d1d2f4cddbda815bb5b9d66a92ac62d
......
.....
.....

But after some time , it times out
Error: trying to reuse blob sha256:01e01442a802ed54e13a0ba59c540bec5658a166e17aec1eb295e63459cade2b at destination: pinging container registry Get "https:///v2/": dial tcp :: i/o timeout

Could you please help me out?

Would --user-mode-networking as explained here , https://docs.podman.io/en/v4.7.2/markdown/podman-machine-set.1.html#user-mode-networking , help?

> podman version
Client: Podman Engine
Version: 4.5.0
API Version: 4.5.0
Go Version: go1.20.2
Git Commit: 75e3c12
Built: Fri Apr 14 20:51:09 2023
OS/Arch: windows/amd64

Server: Podman Engine
Version: 4.9.4
API Version: 4.9.4
Go Version: go1.21.8
Built: Tue Mar 26 15:09:52 2024
OS/Arch: linux/amd64

Thanks!

[abhaybhegde]

Just to add here:

When behind a corporate proxy, after setting the http_proxy , https_proxy and no_proxy envrionment variables on the console, i see i cannot build an image either:

podman build -f Dockerfile -t :v1.0.0
STEP 1/18: FROM registry.access.redhat.com/ubi8/openjdk-17:1.21-1.1752676922
Trying to pull registry.access.redhat.com/ubi8/openjdk-17:1.21-1.1752676922...
Error: creating build container: initializing source docker://registry.access.redhat.com/ubi8/openjdk-17:1.21-1.1752676922: pinging container registry registry.access.redhat.com: Get "https://registry.access.redhat.com/v2/": Forbidden

[abhaybhegde]

@vrothberg , @n1hility - could you please help me out?

[vrothberg]

Thanks for reaching out!

Such errors are usually caused by a proxy, so there is not much I can do remotely. I suggest two things:

1. Check the logs on the proxy and see if they reveal what's going wrong.
2. Update Podman. Both the client and the server are really old and the versions are not in sync.

[abhaybhegde]

Thank you @vrothberg !!, i will have a look at the proxy log and update to latest (v5.5.0 and v1.20.2 for desktop )

I was looking at podman docs and one option which caught my interest is --user-mode-networking
https://docs.podman.io/en/latest/markdown/podman-machine-set.1.html

Would that be an option to explore?

Thanks!

[vrothberg]

Would that be an option to explore?

Good catch! Feel free to try it out.