Instantly crashing synology NAS Docker #166

New Issue

OVERLORD · 2026-02-06T19:23:04+03:00

OVERLORD commented

2026-02-06 19:23:04 +03:00

Originally created by @deten on GitHub (Dec 29, 2018).

Here's my docker run command to create the container:

docker run -d \
    --name=jellyfin-emby-unlocked \
    --net=host \
    --user $XXXX:$XXX \
    -p 8096:8096 \
    -v /volume2/video/TestEmby:/config \
    -v /volume2/video:/media \
    jellyfin/jellyfin

Heres the log:


Unhandled   Exception: System.AggregateException: One or more errors occurred. (Access to   the path '/config/logs/server-63681661975.txt' is denied.) --->   System.UnauthorizedAccessException: Access to the path   '/config/logs/server-63681661975.txt' is denied. --->   System.IO.IOException: Permission denied
--
--- End of inner exception stack trace ---
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess   access, FileShare share, Int32 bufferSize, FileOptions options)
at Emby.Server.Implementations.Logging.FileLogger..ctor(String path)   in /repo/Emby.Server.Implementations/Logging/SimpleLogManager.cs:line 172
at   Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity   severity, CancellationToken cancellationToken) in   /repo/Emby.Server.Implementations/Logging/SimpleLogManager.cs:line 52
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32   millisecondsTimeout, CancellationToken cancellationToken)
at MediaBrowser.Server.Mono.MainClass.Main(String[] args)
Aborted

Originally created by @deten on GitHub (Dec 29, 2018). Here's my docker run command to create the container: ``` docker run -d \ --name=jellyfin-emby-unlocked \ --net=host \ --user $XXXX:$XXX \ -p 8096:8096 \ -v /volume2/video/TestEmby:/config \ -v /volume2/video:/media \ jellyfin/jellyfin ``` Heres the log: ``` Unhandled Exception: System.AggregateException: One or more errors occurred. (Access to the path '/config/logs/server-63681661975.txt' is denied.) ---> System.UnauthorizedAccessException: Access to the path '/config/logs/server-63681661975.txt' is denied. ---> System.IO.IOException: Permission denied -- --- End of inner exception stack trace --- at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at Emby.Server.Implementations.Logging.FileLogger..ctor(String path) in /repo/Emby.Server.Implementations/Logging/SimpleLogManager.cs:line 172 at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellationToken) in /repo/Emby.Server.Implementations/Logging/SimpleLogManager.cs:line 52 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken) at MediaBrowser.Server.Mono.MainClass.Main(String[] args) Aborted ```

OVERLORD closed this issue

2026-02-06 19:23:05 +03:00

OVERLORD commented

2026-02-06 19:23:06 +03:00

@sparky8251 commented on GitHub (Dec 29, 2018):

Try:

docker run -d \
    --name=jellyfin-emby-unlocked \
    --net=host \
    -e UID=XXXX \
    -e GUID=XXXX \
    -p 8096:8096 \
    -v /volume2/video/TestEmby:/config \
    -v /volume2/video:/media \
    jellyfin/jellyfin

The --user and --group switches are deprecated and there is even a check on line 16 and 17 of the dockerfile that should've killed the container if you used them.

It's looking like the user and group aren't setting so the server cannot access its old files. The above should make it run as the specific user/group.

@sparky8251 commented on GitHub (Dec 29, 2018): Try: ``` docker run -d \ --name=jellyfin-emby-unlocked \ --net=host \ -e UID=XXXX \ -e GUID=XXXX \ -p 8096:8096 \ -v /volume2/video/TestEmby:/config \ -v /volume2/video:/media \ jellyfin/jellyfin ``` The `--user` and `--group` switches are deprecated and there is even [a check on line 16 and 17 of the dockerfile](https://github.com/jellyfin/jellyfin/blob/master/Dockerfile) that should've killed the container if you used them. It's looking like the user and group aren't setting so the server cannot access its old files. The above should make it run as the specific user/group.

OVERLORD commented

2026-02-06 19:23:07 +03:00

@deten commented on GitHub (Dec 29, 2018):

Solved using your -e UID and -e GUID format

@deten commented on GitHub (Dec 29, 2018): Solved using your -e UID and -e GUID format

OVERLORD commented

2026-02-06 19:23:09 +03:00

@fuomag9 commented on GitHub (Aug 12, 2021):

I confirm that removing the --user option fixed my issue for me as well

@fuomag9 commented on GitHub (Aug 12, 2021): I confirm that removing the --user option fixed my issue for me as well

OVERLORD referenced this issue

2026-02-07 05:39:35 +03:00

[PR #166] [MERGED] Develop #8200

Sign in to join this conversation.

Branches Tags

master

release-10.11.z

renovate/skiasharp-monorepo

JPVenson-patch-1

renovate/morestachio-5.x

release-10.9.z

openapi-cache

release-10.10.z

explicit-load

explicit-load-v2

feature/entity-framework

only-count-folder-item

fix/ci-workflow-refactor

release-10.8.z

release-10.7.z

EraYaN-add-management-interface

release-10.6.z

release-10.5.z

release-10.4.z

release-10.3.z

release-10.2.z

release-10.1.0

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#166