mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #1792] Opening database fails using the provided docker config #992
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#992
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @NtWriteCode on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/koel/koel/issues/1792
Describe the bug
When trying to install from zero, it looks like koel is unable to connect to the database I just configured.
To reproduce
Steps to reproduce the behavior:
container_name: koeldocker exec --user www-data -it koel bashphp artisan koel:init --no-assetsOutput:
Logfile:
Expected behavior
Not trying to connect to a nonexistent SQLite engine and use my actually set up SQL server container.
Screenshots
Logs attached, UI is not affected
Environment
Your dockerfile controls everything below, hence I won't fill it, should be the default supported ones.
Additional context
This is my first installation, not an upgrade, I'm just a new user trying some cool selfhosted streaming :)
@phanan commented on GitHub (Jul 16, 2024):
First, this is not installing from zero — you're doing some customization on Docker version (which by itself isn't ground zero either). Installing from zero would mean to compile everything from source which, trust me, I've done successfully thousands of times ;)
Anyway, the error isn't related to Koel database, but the search index used by TNTSearch, which is an SQLite db. I'm assuming here there's something wrong with your installation and the search_index volume (found in Docker config) isn't writeable. I'd suggest looking into this direction.
@metzger100 commented on GitHub (Jul 21, 2024):
I have the same Issue with the same storage/logs/laravel.log
search_index volume is empty and not writeable for www-data
ctrl + d
@NtWriteCode commented on GitHub (Jul 22, 2024):
@ metzger100, I haven't yet had time to figure out my actual issue, but it's somehow related to the fact that I'm not using docker volumes, but rather mounting my paths. Probably this ticket would be more appropriate in the docker's repository, but whatever. I'll still have to find out. After correcting the permissions I still couldn't get things together. My user id owns my music files, so it's a bit harder to make it work perfectly with the permissions in the docker...
@phanan commented on GitHub (Jul 22, 2024):
You can always grant www-data the rw permissions to the mounted volume, I’d
assume?
On Mon, Jul 22, 2024 at 10:08 NtWriteCode @.***> wrote:
@metzger100 commented on GitHub (Jul 22, 2024):
That shouldn't be an Issue. I didn't change the permissions of the music folder and it worked perfectly fine. The music folder is owned by root:users. But I didn't investigate further, probably I configured a read/write ACL for www-data. I decided not use Koel after I noticed that proxy authentication is a "Plus" Feature. Plex works just fine for me so I decided not use Koel.
EDIT: www-data has rw rights via an ACL for the music folder.
@kabatp commented on GitHub (May 26, 2025):
@NtWriteCode please add your docker compose yml file (redact passwords and other sensitive content...), and state your OS. I encountered very similar issues today on my TrueNas Scale installation and successfully fixed them, I may be able to help.
@NtWriteCode commented on GitHub (May 26, 2025):
Sadly I don't have this container anymore, so I guess we can close it as not reproducible. I started using Jellyfin's music service. It looks more awkward and lamer than koel, but it worked on first try with the docker container. Maybe once ever later I'll give it a second shot :)