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
Hello, it's more of a question related to updating the docker version, if you happen to know.
When using volume mount, like described on your ReadMe, Jellyfin is able to generate all web files, and I can modify them ob that mounted folder (through the volume).
When binding the mount directly to the docker folder, however, it fails to create the files, with both jellyfin and linuxserver images, throwing :
[14:23:44] [ERR] [4] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /jellyfin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings.
[14:23:44] [INF] [2] Main: Received a SIGTERM signal, shutting down
Would you happen to know why?
The text was updated successfully, but these errors were encountered:
I've got the same problem. Trying to access the webroot folder through a volume mount in docker compose and am getting nothing but an empty folder, even if I don't create the mount path beforehand. I suspect it has to do with how the image is created, but I don't know a way to work around it.
make a mount point in the docker-compose file if possible and then without creating the folder on your host system recreate the docker container using sudo docker-compose up
Hello, it's more of a question related to updating the docker version, if you happen to know.
When using volume mount, like described on your ReadMe, Jellyfin is able to generate all web files, and I can modify them ob that mounted folder (through the volume).
When binding the mount directly to the docker folder, however, it fails to create the files, with both jellyfin and linuxserver images, throwing :
Would you happen to know why?
The text was updated successfully, but these errors were encountered: