Open mozartilize opened 2 years ago
Please provide a full podman info
@mheon I provided it in the description, is there any information I miss?
That is podman version
not podman info
@mheon my bad
A friendly reminder that this issue had no activity for 30 days.
@mozartilize Are you still seeing this issue with latest podman?
@rhatdan yes, with podman 4.3.1, the issue still happens
@mheon Thoughts?
A friendly reminder that this issue had no activity for 30 days.
@mheon Thoughts?
@mozartilize did you ever try this with crun?
@rhatdan yes, with crun it works
$ cat ~/.config/containers/containers.conf
[engine]
runtime = "crun"
$ docker run --rm -p 8080:80 nginx
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2023/01/07 07:55:45 [notice] 1#1: using the "epoll" event method
2023/01/07 07:55:45 [notice] 1#1: nginx/1.23.2
2023/01/07 07:55:45 [notice] 1#1: built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
2023/01/07 07:55:45 [notice] 1#1: OS: Linux 5.15.85-1-lts
2023/01/07 07:55:45 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 524288:524288
2023/01/07 07:55:45 [notice] 1#1: start worker processes
2023/01/07 07:55:45 [notice] 1#1: start worker process 24
2023/01/07 07:55:45 [notice] 1#1: start worker process 25
2023/01/07 07:55:45 [notice] 1#1: start worker process 26
2023/01/07 07:55:45 [notice] 1#1: start worker process 27
2023/01/07 07:55:45 [notice] 1#1: start worker process 28
2023/01/07 07:55:45 [notice] 1#1: start worker process 29
2023/01/07 07:55:45 [notice] 1#1: start worker process 30
2023/01/07 07:55:45 [notice] 1#1: start worker process 31
2023/01/07 07:55:45 [notice] 1#1: start worker process 32
2023/01/07 07:55:45 [notice] 1#1: start worker process 33
2023/01/07 07:55:45 [notice] 1#1: start worker process 34
2023/01/07 07:55:45 [notice] 1#1: start worker process 35
@AkihiroSuda @kolyshkin @giuseppe Any ideas?
Is the case 2 relevant to the case 1? If not probably it's better to open another issue.
@AkihiroSuda as I mentioned,
Before I run podman system reset, both 2 cases return the same error as case 2.
But I have an update after some testing today that the second case doesn't happen anymore.
The only problem is when I run docker run --rm -p 8080:80 nginx
with DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock
and runc
engine, I get unable to upgrade to tcp, received 409
A friendly reminder that this issue had no activity for 30 days.
could you look in the journal if there is any useful information why it failed?
Could you try dropping the resources
block in the compose file?
Hi,
I'm not sure if my issue is closely related to this one. Please tell me if I need to open a new one.
I have this error unable to upgrade to tcp, received 409 (exec.go:71:0s)
when using piplr as a gitlab-runner:
Preparing the "docker" executor 00:02
Using Docker executor with image quay.io/podman/stable ...
Pulling docker image quay.io/podman/stable ...
Using docker image sha256:f58758d0b5823a50b52ebc24ce4c4a615652a73c879bd69d40f27ae832e2fb15 for quay.io/podman/stable with digest quay.io/podman/stable@sha256:05d6df73cb7303e4e5ba0d2a7c6dcba8add16bb7c7acd6d36d267dafed6b8b75 ...
Preparing environment 00:00
ERROR: Job failed (system failure): prepare environment: unable to upgrade to tcp, received 409 (exec.go:71:0s). Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information
Is is weird because when starting the runner manually with podman start pipglr
it works fine. The above error occurs when the runner is started with systemctl --user start pipglr.service
, which just runs the very same podman start pipglr
command against the very same pipglr container.
I've compared the results of running podman --debug info
in both contexts and saw no differences beside volatile values such as dates or sizes.
My current pipglr image has podman v4.6.1. An older image I created a few months ago with podman 4.4.1 works flawlessly.
The image is built against centos:stream9. Is there any easy way to grab podman releases between v4.4.1 and v4.6.1 for CentOS Stream 9 so I could bisect against podman version? I cannot find any release older than 4.6.0-0.3.el9 anymore.
One thing that I forgot to mention that I managed to run both docker and podman in rootless mode.
I have this error
unable to upgrade to tcp, received 409 (exec.go:71:0s)
when using piplr as a gitlab-runner:
This was https://github.com/containers/podman/issues/19930. Downgrading crun
to 1.8.7
works as a workaround until the fix is released.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue: Case 1:
Having docker, podman installed
export DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock
Run
docker run --rm -p 8080:80 nginx
Describe the results you received: Getting error with message
unable to upgrade to tcp, received 409
Case 2:
Remove docker, only have podman
export DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock
Run nomad
nomad agent -dev
, start a job which runs nginx with docker driverDescribe the results you received:
Additional information you deem important (e.g. issue happens only occasionally):
Before I run
podman system reset
, both 2 cases return the same error as case 2.Output of
podman version
:Output of
podman info
:Output of
docker info
:Click me
``` Client: Context: default Debug Mode: false Plugins: compose: Docker Compose (Docker Inc., 2.11.2) Server: Containers: 2 Running: 0 Paused: 0 Stopped: 0 Images: 1 Server Version: 4.2.1 Storage Driver: overlay Native Overlay Diff: true Using metacopy: false Backing Filesystem: extfs Supports d_type: true Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge macvlan Log: k8s-file none passthrough journald Swarm: inactive Runtimes: runsc crun kata krun runc runj Default Runtime: runc Init Binary: containerd version: runc version: init version: Security Options: seccomp Profile: default Kernel Version: 5.15.74-3-MANJARO Operating System: manjaro OSType: linux Architecture: amd64 CPUs: 12 Total Memory: 15.53GiB Name: witzer ID: 4cab533e-3fdc-4522-801a-b87395e605fb Docker Root Dir: /home/mozart/.local/share/containers/storage Debug Mode: false Experimental: true Live Restore Enabled: false Product License: Apache-2.0 WARNING: No swap limit support WARNING: No cpu cfs quota support WARNING: No cpu cfs period support WARNING: No cpu shares support WARNING: No cpuset support WARNING: IPv4 forwarding is disabled WARNING: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables is disabled ``` **Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)** Yes/No **Additional environment details (AWS, VirtualBox, physical, etc.):**