mirror of
https://github.com/yusing/godoxy.git
synced 2026-01-11 21:10:30 +01:00
Container Panic after v.2.0 #116
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gatesry on GitHub (Oct 26, 2025).
Hi! Thanks for the awesome project. Since v2.0, I can’t get the service to stay up. It panics during startup and the container restarts. If I leave the Docker provider section in config.yml blank/commented, the service starts fine. When it’s present (pointing at socket-proxy), I hit a panic.
godoxy-proxy container logs (startup)
docker-compose.yml
.env
config.yml
@starskyzheng commented on GitHub (Oct 26, 2025):
@kgleeson commented on GitHub (Oct 27, 2025):
Same thing happening here
@coffeespice commented on GitHub (Oct 27, 2025):
Same.
@yusing commented on GitHub (Oct 27, 2025):
Checking now, will fix asap. Sorry for your inconvenience.
@yusing commented on GitHub (Oct 27, 2025):
@kgleeson @starskyzheng @gatesry @coffeespice should be fixed, please update
@starskyzheng commented on GitHub (Oct 27, 2025):
It works. However, another panic:
I use oidc (keycloak)
@yusing commented on GitHub (Oct 27, 2025):
Ok, will check that later
@FrozenFrog commented on GitHub (Oct 27, 2025):
It stills panic after update, do I need to clear cache folder?
@yusing commented on GitHub (Oct 27, 2025):
Run it with env
GOTRACEBACK=all, then send me the full traceback so I can debug@FrozenFrog commented on GitHub (Oct 27, 2025):
It's too weird
@yusing commented on GitHub (Oct 27, 2025):
@FrozenFrog I need a traceback log like this:
GOTRACEBACK=alluser: ...incompose.ymlto run as root temporarily@FrozenFrog commented on GitHub (Oct 27, 2025):
Yes, I have used GOTRACEBACK=all in my environment (docker compose, app service). I use Komodo for container management. As you can see, the godoxy app (whose container name I specified as godoxy-proxy) appears in the Komodo logs. Did I make any mistake anywhere?
@yusing commented on GitHub (Oct 28, 2025):
@FrozenFrog emm, could you try commenting out
user: ${GODOXY_UID:-1000}:${GODOXY_GID:-1000}then run it again once.@FrozenFrog commented on GitHub (Oct 28, 2025):
@yusing commented on GitHub (Oct 28, 2025):
Thank you so much, will have a look and fix it asap.
@yusing commented on GitHub (Oct 28, 2025):
@FrozenFrog @starskyzheng see if it still happen in v0.20.3
@FrozenFrog commented on GitHub (Oct 28, 2025):
It stills there, I will PM you on discord to send more logs
@abjoseph commented on GitHub (Oct 28, 2025):
Hi @yusing FYI - Just adding myself as one more data-point having this panic error. My config/setup is near identical to @FrozenFrog.
Also, FYI - I've been using the same instance/setup since the beginning of godoxy (then go-proxy), and have just been steadily updating image and config since, not sure if that makes a difference but figured I'd mention.
@yusing commented on GitHub (Oct 29, 2025):
I've asked @FrozenFrog and his issue has resolved, make sure you have the image up-to-date. If it still happens, please send me the log.
@gatesry commented on GitHub (Oct 29, 2025):
Latest version worked! Thank you.
@abjoseph commented on GitHub (Oct 30, 2025):
@yusing I've attached the full traceback logs. Let me know if you need the other configs, though they're nearly 1-1 with what has been shared above.
godoxy_logs.txt
Setup/Config:
Frontend: v0.20.3
Backend: v0.20.4