Docker image won't finish startup #73
Comments
|
Hi, thanks for pasting the container logs here. Could you please attach the laravel logs ? They are located at |
|
Thx for the fast reply :) Sorry, the directory doesn't exist. How can I activate them? Can't find the info in the docs. |
|
Now it works just fine, Koel instance is started without any problems. I have no clue what went wrong. No configuration was changed between the last 5 runs. I'll watch it for the next few days and let you know if the error occures again. |
|
I have the same issue. |
Same issue for me. Does anyone have an idea of how to resolve this issue? |
|
I found out that the container took up to 30 minutes to start. so there never was an issue for me in the end. |
|
Have had this issue, noticed the healthcheck was set to 5 minutes. If using Traefik, it will not pass through requests to the server until at least one healthcheck has successfully completed. Thus it will take 5 minutes after starting the container for it to be available on the Traefik interface. You can disable this by setting: in the docker-compose.yml file. This will disable healthchecks and allow the service to be immediately available via Traefik. |
|
I have the same issue. Running the Docker image inside CapRover, but have no way to disable the healthcheck. So if the container needs to reboot for whatever reason, Koel is unavailable for 5 minutes. Would it be possible to make the healthcheck in the Dockerfile optional? Or make the interval shorter until the first success? |
any update here? healthcheck: |
Seems like you have the same issue i had. |
|
I'm attempting to deploy koel via docker swarm stack file. The docker daemon isn't able to start the webserver container. Here are the logs: Finally after several minutes, 10+, koel succesfully started. Something odd is definitely going on here. Stackfile used: version: '3'
services:
koel:
image: phanan/koel:6.12.0
depends_on:
- database
ports:
- 8765:80
environment:
- DB_CONNECTION=pgsql
- DB_HOST=database
- DB_USERNAME=koel
- DB_DATABASE=koel
- DB_PASSWORD=<redacted>
volumes:
- "<redacted>:/music:ro"
- koel-covers:/var/www/html/public/img/covers
- koel-search-index:/var/www/html/storage/search-indexes
networks:
- homelab
deploy:
placement:
constraints:
- node.hostname == <redacted>
labels:
- "traefik.enable=true"
- "traefik.docker.network=homelab"
# ROUTER
- "traefik.http.routers.koel.rule=Host(`<redacted>`)"
- "traefik.http.routers.koel.entrypoints=websecure"
- "traefik.http.routers.koel.service=koel"
# SERVICE
- "traefik.http.services.koel.loadbalancer.server.port=80"
database:
image: postgres:13
volumes:
- koel-pgdata:/var/lib/postgresql/data'
environment:
- POSTGRES_DB=koel
- POSTGRES_USER=koel
- POSTGRES_PASSWORD=<redacted>
networks:
- homelab
deploy:
placement:
constraints:
- node.hostname == <redacted>
volumes:
koel-covers:
driver: local
driver_opts:
type: nfs
o: addr={{nfs_server}},nfsvers=4.1,rw,nolock,soft
device: :/swarm/stacks/koel/covers
koel-search-index:
driver: local
driver_opts:
type: nfs
o: addr={{nfs_server}},nfsvers=4.1,rw,nolock,soft
device: :/swarm/stacks/koel/search_index
koel-pgdata:
driver: local
driver_opts:
type: nfs
o: addr={{nfs_server}},nfsvers=4.1,rw,nolock,soft
device: :/swarm/stacks/koel_db/
networks:
homelab:
external: true |
|
Any update on this? Still an issue in 2025 .......... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current state is permanently
startingand the instance cannot be accessed over the browser.Setup:
Logs:
The text was updated successfully, but these errors were encountered: