Cannot resolve internal host

[DukeReno]

Container platform

OCP 4

Version

No response

OS version of the container image

No response

Bugzilla, Jira

No response

Description

using the image 3.11 python with centos 9, getting this error using Github enterprise

this issue seems to repeat with centos packages

can provide more info if you guys need

Reproducer

No response

[frenzymadness]

Thanks for the report. This looks weird. @phracek and @pkubatrh any idea?

Please also tell us where the cluster is hosted. If you run a container there manually, does the name resolution work? It also seems that you have some proxy configured. Is the traffic going to the name resolver affected or ignored by the proxy?

Honestly, this does not seem like something a configuration in the container or image can affect. If you want, I can try to provide some debugging steps but an administrator of your cluster will probably know more about the specifics of your configuration.

[DukeReno]

can you share the debugging steps, we are trying to contact the admin and see if its the case of the proxy or something else.

[frenzymadness]

I'd try to run an empty container with Centos stream 9 in it and test the name resolution inside of it manually. If that works fine, the problem has to be in the settings of the application container. Then I'd try to track the network traffic to see what nameserver the process in the container tries to contact and whether it's accessible or not. Also, if you have access to the internet, you can try to drop proxy settings first to see whether they are causing any troubles or not.

[DukeReno]

FROM quay.io/sclorg/python-311-c9s:c9s

is this the right image? we are creating the container and trying out what you said, just making sure we are not pulling something unknown or different

[frenzymadness]

Yes, it is. That's the latest one we have for Python 3.11 on Centos stream 9.

If you want to investigate the whole chain it's built like this:

• quay.io/sclorg/python-311-c9s:c9s, on the top of
• quay.io/sclorg/s2i-base-c9s:c9s, on the top of
• quay.io/sclorg/s2i-core-c9s:c9s, on the top of
• quay.io/centos/centos:stream9

So if you want to test a clean (empty) one, take quay.io/centos/centos:stream9.

[DukeReno]

do you know on which entrypoint should I used on the dockerfile to load the image into a container?

[frenzymadness]

I don't understand the question. You can run bash in all of them for interactive testing.