goaway: goaway fails to start due to "failed to create request_log table: Binary was compiled with 'CGO_ENABLED=0'"
New goaway deployment fails to start.
docker-compose.yml:
services:
goaway:
image: pommee/goaway:latest
volumes:
- goaway_data:/app
container_name: goaway
environment:
- DNS_PORT=${DNS_PORT:-53}
- WEBSITE_PORT=${WEBSITE_PORT:-8080}
ports:
- "${DNS_PORT:-53}:${DNS_PORT:-53}/udp"
- "${DNS_PORT:-53}:${DNS_PORT:-53}/tcp"
- "${WEBSITE_PORT:-8080}:${WEBSITE_PORT:-8080}/tcp"
cap_add:
- NET_BIND_SERVICE
- NET_RAW
volumes:
goaway_data:
name: goaway_data
Docker logs:
goaway | Starting goaway...
goaway | 2025/05/23 19:27:35 [WARN] failed to set journal_mode to WAL
goaway | 2025/05/23 19:27:35 [ERROR] failed while initilizing database: failed to create request_log table: Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub
goaway | goaway process exited with code 1. Restarting...
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 17 (9 by maintainers)
@pommee I also ran into that issue with the PTR records. The issue for me was that I ran the application on a VPS that had local DNS for the hosting network. I disabled the local DNS so that goaway could take over. The internal queries in that cased failed and I think for some reason it starts a flood of them, not sure if that is in goaway or if the service that requests them starts to blast. Then I could only kill the app and restart. In that case it had trouble downloading the default blacklist from github because it tries to load that on startup, before the DNS server is initialized. That caused the blacklist crash (and therefor my pull request to return the errors). With my fix to bind goaway on only the external address and having the VPS local DNS on the local interface, I could give goaway my local DNS as upstream and then it worked.