The upgrade to Jellyfin 10.11.0 requires a `/tmp/` of at least 2G. My systemd-nspawn container only provided 1.6G. To resize it I added `TemporaryFileSystem=/tmp:nosuid,size=2G` under the `[Files]` section in its `.nspawn` file. After a restart Jellyfin started its migrations.
I'm not sure if this is the correct way but it works and I can roll back the change after the upgrade.
The container knows of two `/tmp` mounts now. The latter is mounted over the first one. I'd prefer if I could change the size of the first one.
```
root@jellyfin:~# mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=1622240k,nr_inodes=409600,uid=1660485632,gid=1660485632,inode64)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=2097152k,uid=1660485632,gid=1660485632,inode64)
```
Turns out, it's not only the migrations requiring the `/tmp` to be at least 2G. I cannot roll back the change.
Other than that, I had this during `apt update; apt upgrade -y; apt full-upgrade -y; apt autoremove -y`:
`
Setting up libjemalloc2:amd64 (5.3.0-1) ...
Setting up jellyfin-server (10.11.0+deb12) ...
Installing new version of config file /etc/default/jellyfin ...
failed to find libjemalloc on system
dpkg: error processing package jellyfin-server (--configure):
installed jellyfin-server package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of jellyfin:
jellyfin depends on jellyfin-server; however:
Package jellyfin-server is not configured yet.
dpkg: error processing package jellyfin (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u13) ...
Errors were encountered while processing:
jellyfin-server
jellyfin
E: Sub-process /usr/bin/dpkg returned an error code (1)
`
But I didn't had to do anything to fix it?!
Fluchtkapsel