-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Podman version 3.0.2 failed to pull localhost images, everytime trying to pull from registry #11181
Comments
When you are using Also, I note that this looks like a custom-crafted systemd unit - we strongly recommend you use |
@mheon
systemd[1]: Started SC4S Container. I will give a hit with |
With help of
With above configuration podman started successfully with container-splunksyslog.service
But when I am checking the podman logs, I am seeing below errors.
I am unable to identify, why this issue is occurring. Also If I am trying to run with
then service is not starting. I have most of my HEC configuration in |
Podman issue resolved, hence closing this issue. |
Podman issue resolved, hence closing this issue. |
This issue is there in 3.4.2. |
Please open a new issue |
I am trying to use podman existing images but it's failing, either it's failing to load the image from localhost or it's going to pull the image from registry -
podman --version
podman version 3.0.2-dev
OS - RHEL 8
podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/splunk/scs v1.12.0 ac68a53e5a7e 17 months ago 495 MB
localhost/sc4slocal offlineimage ac68a53e5a7e 17 months ago 495 MB
"
podman run localhost/sc4slocal:offlineimage
" OR "podman run sc4slocal:offlineimage
"syslog-ng checking config
sc4s version=v1.12.0
syslog-ng starting
Aug 10 11:10:27 7a370d484433 syslog-ng[1]: syslog-ng starting up; version='3.25.1'
Aug 10 11:10:27 7a370d484433 syslog-ng-config: sc4s version=v1.12.0
This is running fine
But Whenever I tried to run from /lib/systemd/system/sc4s.service It will start creating problems -
Podman + systemd = https://splunk-connect-for-syslog.readthedocs.io/en/latest/gettingstarted/podman-systemd-general/
Read-First = https://splunk-connect-for-syslog.readthedocs.io/en/latest/gettingstarted/#offline-container-installation
Configuration -
run the configuration -
Issue while running above command-
If I set in configuration -
systemd[1]: Started SC4S Container.
podman[3042091]: Trying to pull registry.redhat.io/sc4slocal:offlineimage...
podman[3042091]: Get "https://registry.redhat.io/v2/": dial tcp 184.87.7.162:443: i/o timeout
podman[3042091]: Trying to pull docker.io/library/sc4slocal:offlineimage...
podman[3042091]: Get "https://registry-1.docker.io/v2/": dial tcp 107.23.149.57:443: i/o timeout
podman[3042091]: Error: 3 errors occurred while pulling:
podman[3042091]: * Error initializing source docker://registry.access.redhat.com/sc4slocal:offlineimage: error pinging docker registry registry.acce>
podman[3042091]: * Error initializing source docker://registry.redhat.io/sc4slocal:offlineimage: error pinging docker registry registry.redhat.io: G>
podman[3042091]: * Error initializing source docker://sc4slocal:offlineimage: error pinging docker registry registry-1.docker.io: Get "https://regis>
systemd[1]: sc4s.service: Main process exited, code=exited, status=125/n/a
systemd[1]: sc4s.service: Failed with result 'exit-code'.
If I set in configuration -
systemd[1]: Started SC4S Container.
podman[3054347]: Trying to pull localhost/sc4slocal:offlineimage...
podman[3054347]: time="2021-08-10T12:37:16Z" level=warning msg="failed, retrying in 1s ... (1/3). Error: Error initializing source docker://localhost>
podman[3054347]: time="2021-08-10T12:37:17Z" level=warning msg="failed, retrying in 2s ... (2/3). Error: Error initializing source docker://localhost>
podman[3054347]: time="2021-08-10T12:37:19Z" level=warning msg="failed, retrying in 4s ... (3/3). Error: Error initializing source docker://localhost>
podman[3054347]: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused
podman[3054347]: Error: Error initializing source docker://localhost/sc4slocal:offlineimage: error pinging docker registry localhost: Get "https://lo>
systemd[1]: sc4s.service: Main process exited, code=exited, status=125/n/a
Can anyone please help why this is behaving like this, have disabled the PULL from configuration but still it's going to pull.
Earlier I was using tag - latest not I have replaced with offlineimage but still same issue.
#7699
#9111
https://stackoverflow.com/questions/63970144/podman-play-does-not-pull-localhost-image-get-https-localhost-v2-dial-tcp
The text was updated successfully, but these errors were encountered: