Open RealTriassic opened 7 months ago
You probably have to set the DOCKER_HOST environment variable to point at the podman.sock socket.
You probably have to set the DOCKER_HOST environment variable to point at the podman.sock socket.
This was already done, otherwise servers wouldn't be able to start even with all the workarounds mentioned above.
I am aware of the first two parts of this issue (OOM killer and the weird container update errors). I'm unsure why the container update errors out, or what exactly causes it, but everything seems to work fine regardless.
The HTTP 409 error is interesting as it was either fixed in a later Podman release or there was a regression in Wings or the Docker API somewhere.
I am aware of the first two parts of this issue (OOM killer and the weird container update errors). I'm unsure why the container update errors out, or what exactly causes it, but everything seems to work fine regardless.
The HTTP 409 error is interesting as it was either fixed in a later Podman release or there was a regression in Wings or the Docker API somewhere.
Oom killer is caused by CgroupV2 Disabling OOM killer is not possible at all on cgroupV2 crun will give error
Current Behavior
Out of curiosity and boredom, I decided to try Podman with Wings after seeing that some people have gotten it working, but ran into a couple issues that prevent this from working smoothly.
Stacktrace: Error response from daemon: Not Found environment/docker: could not update container github.com/pterodactyl/wings/environment/docker.(Environment).InSituUpdate github.com/pterodactyl/wings/environment/docker/container.go:129 github.com/pterodactyl/wings/server.(Server).SyncWithEnvironment github.com/pterodactyl/wings/server/update.go:51 github.com/pterodactyl/wings/server.(Server).Sync github.com/pterodactyl/wings/server/server.go:200 github.com/pterodactyl/wings/server.(Server).onBeforeStart github.com/pterodactyl/wings/server/power.go:174 github.com/pterodactyl/wings/server.(Server).HandlePowerAction github.com/pterodactyl/wings/server/power.go:131 github.com/pterodactyl/wings/router/websocket.(Handler).HandleInbound github.com/pterodactyl/wings/router/websocket/websocket.go:363 github.com/pterodactyl/wings/router.getServerWebsocket.func3 github.com/pterodactyl/wings/router/router_server_ws.go:85 runtime.goexit runtime/asm_amd64.s:1598
ERROR: [Nov 18 14:50:35.719] failed to handle server crash error=failed to start server after crash detection: environment/docker: failed to attach to container: environment/docker: error while attaching to container: unable to upgrade to tcp, received 409 server=89b3e647-dc1a-4a58-85d8-7e35b7d0ab1c
Stacktrace: unable to upgrade to tcp, received 409 environment/docker: error while attaching to container github.com/pterodactyl/wings/environment/docker.(Environment).Attach github.com/pterodactyl/wings/environment/docker/container.go:61 github.com/pterodactyl/wings/environment/docker.(Environment).Start github.com/pterodactyl/wings/environment/docker/power.go:121 github.com/pterodactyl/wings/server.(Server).HandlePowerAction github.com/pterodactyl/wings/server/power.go:135 github.com/pterodactyl/wings/server.(Server).handleServerCrash github.com/pterodactyl/wings/server/crash.go:90 github.com/pterodactyl/wings/server.(*Server).OnStateChange.func1 github.com/pterodactyl/wings/server/server.go:324 runtime.goexit runtime/asm_amd64.s:1598
environment/docker: failed to attach to container failed to start server after crash detection github.com/pterodactyl/wings/server.(Server).handleServerCrash github.com/pterodactyl/wings/server/crash.go:90 github.com/pterodactyl/wings/server.(Server).OnStateChange.func1 github.com/pterodactyl/wings/server/server.go:324 runtime.goexit runtime/asm_amd64.s:1598
container@pterodactyl~ Error Event [146a8c18-d9b2-4c30-9f94-5f1dee081c9b]: environment/docker: failed to attach to container: environment/docker: error while attaching to container: unable to upgrade to tcp, received 409