[GH-ISSUE #853] SQLite Bind Address already in use #399

New issue

Closed

opened 2026-02-25 23:34:08 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 23:34:08 +03:00

Owner

Originally created by @evensong-sys on GitHub (Mar 4, 2024).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/853

Data

Shiori version: Docker Latest
Database Engine: SQLite
Operating system: Linux/Dcoker

This probably isn't actually an issue with Shiori, but some kind of screw up on my part. I am trying to set up Shiori in a Docker container using SQLite, however, I realized that the .db file is not being created. So I tried running " docker exec -it shiori shiori serve" to see if I could get it to start/create the .db file, but I get an error message:
"INFO[2024-03-04T05:11:08Z] Serve shiori in :8080 /
FATA[2024-03-04T05:11:08Z] Server error: listen tcp :8080: bind: address already in use "

docker-compose.yml:
shiori: image: ghcr.io/go-shiori/shiori:latest container_name: shiori restart: "unless-stopped" networks: - udms ports: - 8088:8080 volumes: - $DOCKERDIR/appdata/shiori:/shiori environment: - PUID=$PUID - PGID=$PGID - TZ=$TZ - $DOCKERDIR/appdata/shiori=/shiori

I'm not sure how to fix this. I thought maybe it was a conflict with another docker container that also uses SQLite, so I stopped that container with docker compose down command. But that doesn't seem to fix the error.

Originally created by @evensong-sys on GitHub (Mar 4, 2024). Original GitHub issue: https://github.com/go-shiori/shiori/issues/853 ## Data - **Shiori version**: Docker Latest - **Database Engine**: SQLite - **Operating system**: Linux/Dcoker This probably isn't actually an issue with Shiori, but some kind of screw up on my part. I am trying to set up Shiori in a Docker container using SQLite, however, I realized that the .db file is not being created. So I tried running " docker exec -it shiori shiori serve" to see if I could get it to start/create the .db file, but I get an error message: "INFO[2024-03-04T05:11:08Z] Serve shiori in :8080 / FATA[2024-03-04T05:11:08Z] Server error: listen tcp :8080: bind: address already in use " docker-compose.yml: ` shiori: image: ghcr.io/go-shiori/shiori:latest container_name: shiori restart: "unless-stopped" networks: - udms ports: - 8088:8080 volumes: - $DOCKERDIR/appdata/shiori:/shiori environment: - PUID=$PUID - PGID=$PGID - TZ=$TZ - $DOCKERDIR/appdata/shiori=/shiori` I'm not sure how to fix this. I thought maybe it was a conflict with another docker container that also uses SQLite, so I stopped that container with docker compose down command. But that doesn't seem to fix the error.

kerem

2026-02-25 23:34:08 +03:00

closed this issue
added the
tag:stale
label

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@Monirzadeh commented on GitHub (Mar 4, 2024):

about database I think it is duplicate #546
What's output of docker ps?
It seams shiori use 8080 inside container so you can't use 8080 again.
You can see everythings from inside of container with
docker exec -it /bin/sh and than something like netstat -a -b

@Monirzadeh commented on GitHub (Mar 4, 2024): about database I think it is duplicate #546 What's output of `docker ps`? It seams shiori use 8080 inside container so you can't use 8080 again. You can see everythings from inside of container with `docker exec -it /bin/sh` and than something like `netstat -a -b`

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@evensong-sys commented on GitHub (Mar 4, 2024):

docker ps output:
https://gist.github.com/ordinarysimplicity/6cf7f3ad9111c259c7ac73bf0f92ab2a

I have several services that use 8080 internally, but I didn't think the internal ports could conflict across containers... maybe I'm wrong in thinking that? Though this would be the first time I've had this issue.

@evensong-sys commented on GitHub (Mar 4, 2024): docker ps output: https://gist.github.com/ordinarysimplicity/6cf7f3ad9111c259c7ac73bf0f92ab2a I have several services that use 8080 internally, but I didn't think the *internal* ports could conflict across containers... maybe I'm wrong in thinking that? Though this would be the first time I've had this issue.

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@Monirzadeh commented on GitHub (Mar 4, 2024):

When you run
docker exec -it shiori shiori serve you run shiori again inside container that shiori already run and used 8080.
If docker exec -it shiori /bin/sh you can see container from inside.
Do you check that issue I mention?

@Monirzadeh commented on GitHub (Mar 4, 2024): When you run `docker exec -it shiori shiori serve` you run shiori again inside container that shiori already run and used 8080. If `docker exec -it shiori /bin/sh` you can see container from inside. Do you check that issue I mention?

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@fmartingr commented on GitHub (Apr 2, 2024):

Using docker exec -it shiori shiori serve over the running shiori container won't work because Shiori is already running on port 8080. Can you share the container logs?

@fmartingr commented on GitHub (Apr 2, 2024): Using `docker exec -it shiori shiori serve` over the running shiori container won't work because Shiori is already running on port 8080. Can you share the container logs?

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@stale[bot] commented on GitHub (May 3, 2024):

This issue has been automatically marked as stale because it has not had any activity for quite some time.
It will be closed if no further activity occurs.
Thank you for your contributions.

@stale[bot] commented on GitHub (May 3, 2024): This issue has been automatically marked as stale because it has not had any activity for quite some time. It will be closed if no further activity occurs. Thank you for your contributions.