🐛[BUG] Restarting the docker container results in a faulty index.html file. #3
Description
Describe the bug
On Docker restart, index.html still persists as the container ID is still the same. It appears that jellyfin-javascript-injector might be corrupting index.html on reboot (maybe applying changes twice?).
It's also possible that a mix of multiple plugins are causing this to happen.
To Reproduce
Steps to reproduce the behavior:
Start Jellyfin container.
docker restart jellyfin
Jellyfin successfully boots, but you are greeted with a black screen.
Expected behavior
A clear and concise description of what you expected to happen.
Jellyfin to continue functioning as normal.
Screenshots
If applicable, add screenshots to help explain your problem.
Jellyfin Version and Installation method (please complete the following information):
- Jellyfin Version: [e.g. 10.9.9, 10.10.7]
- Installation Method: [e.g. Docker, Linux]
Logs that might be helpful
I put the index.html before first boot, after first boot, after restart.
https://gist.github.com/xNinjaKittyx/b55ea393e2a474be7005df41ea6d4510
In order to get around this, I modified a startup script to initially just change the ownership, to also save the original index.html and reapply on every boot.
#!/bin/bash
# Define file paths
SOURCE_FILE="/opt/index.html"
DEST_FILE="/usr/share/jellyfin/web/index.html"
# Check if /opt/index.html exists
if [ -f "$SOURCE_FILE" ]; then
echo "$SOURCE_FILE exists. Copying to $DEST_FILE."
cp "$SOURCE_FILE" "$DEST_FILE"
else
echo "$SOURCE_FILE does not exist. Creating a copy from $DEST_FILE."
cp "$DEST_FILE" "$SOURCE_FILE"
fi
# Set ownership to abc:abc for the destination file
chown abc:abc "$DEST_FILE"
# Print completion message
echo "Operation completed successfully."