Closed Aterfax closed 1 year ago
Google claims you have run out of space https://social.msdn.microsoft.com/Forums/en-US/12666856-a40e-4e6b-9243-3d3ebd992971/not-enough-storage-is-available-to-process-this-command
Not on any of my filesystems/disks/mounts that I see using df
. Likewise plenty of RAM free. Since the previous major version is working, I expect this is not a problem with the filesystems being bind mounted, suggests that the container processes are trying to write somewhere they cannot?
Meanwhile, updating docker to version 20.10.21 has also not resolved the issue.
I ran into the same issue on ubuntu focal and docker 19. After upgrading my docker to version 20.10.21
everything seems to work again.
Meanwhile, updating docker to version 20.10.21 has also not resolved the issue.
As previous mentioned. I tried that and it has not resolved the issue.
That's not the only reason/solution mentioned. Add the security opt
You've redacted all the useful information from your config, but my guess is that you're running /config on a remote mount or some kind of union fs and it's causing a problem with the dotnet CLR, probably related to the new syscalls.
You've redacted all the useful information from your config, but my guess is that you're running /config on a remote mount or some kind of union fs and it's causing a problem with the dotnet CLR, probably related to the new syscalls.
Config is on a normal disk based FS mount (for a VM) as are all the mounts.
I need to give the security opt a go but not at a terminal at the mo to give it a go.
I'm expecting it's related to the rebase on jammy for the container but not exactly sure what is causing it.
Are there any filesystems that cause a problem? Btrfs?
Remote filesystems (NFS, SMB) are not supported for /config.
Union filesystems (e.g. mergerfs) can cause issues for some containers in certain configurations.
USB-mounted filesystems can cause issues due to default permissions.
I was running into this issue, but the securityopt cleared it up for me. Thanks!
security_opt:
- seccomp=unconfined
Has solved the issue on my VM but this seems a bit questionable as a long term solution.
The long term solution is update your docker engine and update your host.
Any version of Docker released this year supports the necessary syscalls and, in most cases, is sufficient to fix the issue. In some cases if you have an old kernel that doesn't support the syscall properly either than you still need the seccomp options set.
If you have both an up to date docker install and a recent kernel then you'll have to look into other possible causes because we haven't seen any other reported issues.
Beats me, as far as I know this is the most up to date Ubuntu 22.04.1 LTS can be.
docker --version
Docker version 20.10.22, build 3a2c30b
uname -a
Linux hostname 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Ran another apt update and reboot with no fix (kernel 5.15.0-53 --> 5.15.0-56).
Worked up a new docker-compose.yml and the issue appears to have vanished. Wonder if some part retained configuration via Portainer left something incompatible which has been cleared out by the new compose file /container.
Others may also resolve their future issues by fully tearing down their config and fully remaking their configuration.
Not entirely sure what the issue was being caused by (I don't believe this was kernel or docker versions given my first post), that said, closing as resolved.
Is there an existing issue for this?
Current Behavior
Latest docker image fails to start.
sha256:2bf40f286d4da70f81a70755ffa21bdd7f1ba2e5b83e66548568016a40740b8a:
Failed to create CoreCLR, HRESULT: 0x80070008
Reverting to the last major version (linuxserver/jellyfin:10.8.7) fixes the issue (for me.)
Saw https://docs.linuxserver.io/faq#jammy but since my docker version is greater than 20.10.10 it is probably not that.
Expected Behavior
Jellyfin should start normally.
Steps To Reproduce
Update your container to the latest version of the image.
Environment
CPU architecture
x86-64
Docker creation