You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked that someone hasn't already asked about the same issue
Behaviour
I'm trying to self-host atuin using docker image. Containers seem to start fine. Port 8888 is being listened on, but curl http://localhost:8888 prints out curl: (56) Recv failure: Connection reset by peer after long wail. There seems to be no way to communicate with the server
I'm not using systemd service, just starting containers with docker compose up -d. Not sure if it matters or not.
I've tried versions 15, 16 and 17 with identical result, so I'm coming to conclusion that it may not be an issue with atuin. I'd appreciate any help though, because I'm stuck and have no idea how to debug the cause. Cheers!
Logs
I'm not entirely sure how to access the logs. Output of docker logs <container_id> with just ATUIN_LOG=debug is empty. When I also add RUST_LOG=debug it spits out logs related to database (no errors here that I can see).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Operating System
ubuntu 22.04
Shell
bash 5.2.15
Version
v17.0.0 (Default)
Self hosted
Search the issues
Behaviour
I'm trying to self-host atuin using docker image. Containers seem to start fine. Port 8888 is being listened on, but
curl http://localhost:8888
prints outcurl: (56) Recv failure: Connection reset by peer
after long wail. There seems to be no way to communicate with the serverI'm not using systemd service, just starting containers with
docker compose up -d
. Not sure if it matters or not.I've tried versions 15, 16 and 17 with identical result, so I'm coming to conclusion that it may not be an issue with atuin. I'd appreciate any help though, because I'm stuck and have no idea how to debug the cause. Cheers!
Logs
I'm not entirely sure how to access the logs. Output of
docker logs <container_id>
with justATUIN_LOG=debug
is empty. When I also addRUST_LOG=debug
it spits out logs related to database (no errors here that I can see).Extra information
docker-compose.yml:
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions