Known Issues on Info :: LinuxServer.io

[Resolved] Known Issue: curl endless loop with 3.x Kernels

Sat, 30 Dec 2023 18:00:00 +0000

Update

The Alpine maintainers have backported a fixed version of the affected library to 3.19 and we have published a new version of our 3.19 base image that should resolve the issues with 3.x kernels. It will take a few days for all affected downstream images to push new builds, but any image released from this point onwards will include the fix.

Original Post

There is a known issue with the version of curl currently shipped with Alpine 3.19 and 3.x kernels, causing an endless loop to hang containers, usually on startup. The 3.x kernel line has been End of Life since 2017, but some prebuilt systems such as older Synology NAS units are still running it. At time of posting, around 10% of our images have already been rebased to Alpine 3.19 and are therefore affected by this issue, and this number will continue to rise over the next few months.

While a fix has been applied to the affected upstream library we do not have an ETA for if or when it will find its way into the version of curl shipped with Alpine 3.19.

Workaround

As a workaround you can revert to an older tag from before the image was rebased to Alpine 3.19, but please be aware that older tags do not receive updates. Refer to the Changelog in the Readme to see when the change was made for a given image. For Unraid users this will require you to edit the container and under the Advanced options change the Repository to append the required tag.

[Resolved] Known Issue: qBittorrent 4.6.1 Web UI Password

Wed, 22 Nov 2023 18:00:00 +0000

Fix has been released, update to 4.6.2. The readme has been updated to reflect how the password for new installs are handled going forward

There is a known issue with qBittorrent 4.6.1, due to an upstream change which changes the Web UI password to a random value on startup if you have not changed it from the default. This change has been made for security reasons due to hackers exploiting users who have exposed their instances to the internet with default credentials.

Due to an upstream bug the generated password is not printed to the container logs, making it impossible to log in.

Workaround

As a workaround until a fix can be released, start the container with the :version-4.6.0-r0 image tag, login to the Web UI using the old default credentials, and change the admin account password. You will then be able to switch back to the :version-4.6.1-r0 or :latest tags. For Unraid users this will require you to edit the container and under the Advanced options change the Repository to append the required tag; you can find step-by-step instructions here.

[Resolved] Known Issue: Discourse Emails

Thu, 20 Jul 2023 20:00:00 +0000

Due to a misconfiguration that occurred during a routine restore of the database for our Discourse Forums, registered users may have recieved unwanted email notifications over the last 24 hours.

This issue has now been resolved and we apologise for any inconvenience caused.

[Resolved] Known Issue: MariaDB Check and Repair

Mon, 29 May 2023 12:00:00 +0000

There is a known issue with MariaDB when updating the container image to a new version. If a database upgrade is required and user databases are not in a healthy state, then the MariaDB service may fail to start.

MariaDB version updates (ex: 10.6.x to 10.11.x) can happen when updating the container image. Upgrading user databases is done manually by running a command.

Recovery Procedure

If you have recently updated your container image and your container logs show repeating entries of:

Caught SIGTERM signal!

Roll back the container image to a previous tag (ex: lscr.io/linuxserver/mariadb:10.6.13 assuming this was the version you were running when things were last working)
Run the check, repair, analyze, and optimize commands, watch for any issues
Update the container image to the new tag (ex: lscr.io/linuxserver/mariadb:10.11.3 or lscr.io/linuxserver/mariadb:latest)
Run the upgrade command

This should get MariaDB running again with your user databases in a healthy state.

Check and Repair

If user databases are not in a healthy state (sometimes caused by a failed upgrade), it may be remedied by running:

mariadb-check -u root -p<PASSWORD> -c -A # check all databases for errors
mariadb-check -u root -p<PASSWORD> -r -A # repair all databases
mariadb-check -u root -p<PASSWORD> -a -A # analyze all databases
mariadb-check -u root -p<PASSWORD> -o -A # optimize all databases

After running the above commands, you may need to run the upgrade command again.

Upgrading

When this container initializes, if MYSQL_ROOT_PASSWORD is set an upgrade check will run. If an upgrade is required the log will indicate the need stop any services that are accessing databases in this container, and then run the command:

mariadb-upgrade -u root -p<PASSWORD>

Closing Notes

If you are running MariaDB databases in production, we always recommend pinning the container image to a specific version tag, such as lscr.io/linuxserver/mariadb:10.6.13-r0-ls97, and planning any upgrades so that you can test and monitor them.

[Resolved] Known Issue: Portainer & Synology Docker UI

Mon, 22 May 2023 12:00:00 +0000

Update

The underlying issue still exists for both Portainer and the Synology container management UI, but the primary driver of issues has largely dissipated and so we are unpinning this notice.

Original Post

There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.

This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our SABnzbd image the PATH environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start. This is likely to become more common in the future, and there is not a practical or scalable solution that we can apply from our end to avoid this issue.

Our position remains that we provide support only for containers created and updated using Docker Compose, the Docker CLI, or using our Unraid templates, and not any 3rd party tools.

[Resolved] Known Issue: Heimdall 2.5.0 & 2.5.1 Releases

Fri, 25 Nov 2022 16:00:00 +0000

Update

Version 2.5.2 has been released to fix the install issues. Users running 2.5.1 or below should look to upgrade to the version-v2.5.2 or latest tags.

Original Post

There is a known issue with the Heimdall 2.5.0 and 2.5.1 releases causing broken installs for some users. If you are experiencing issues please roll back to the version-v2.4.15 tag until a fix can be published. We will update this post as necessary.

[Resolved] Known Issue: lscr.io Unreachable

Sun, 22 May 2022 16:00:00 +0000

Update

DNS propagation has completed and all services should now be accessible. If you’re still experiencing connection issues please clear your DNS cache and try again.

Original Post

Due to an issue with our domain registrar the lscr.io domain is has been unreachable for part of the day. The underlying problem has been resolved and we are now waiting for DNS propagation to complete so that we can resume normal operations.

If you are experiencing issues with pulling images from lscr.io you can use ghcr.io, docker.io, or any other mirror in the interim.

[Resolved] Known Issue: nzbhydra2 Stable v4.3.1-ls52 and later

Thu, 05 May 2022 12:00:00 +0000

Update

We have identified the root cause of the issue and documented the available solutions here: https://docs.linuxserver.io/faq#jammy

Original Post

There is a known compatibility issue with our nzbhydra2 image Stable branch versions v4.3.1-ls52 and later and older versions of the Docker engine on some amd64 platforms. If you experience Java errors on startup in the form of:

ERROR - Unable to determine java version; make sure Java is installed and callable.

Please ensure that your Docker install is updated to at least version 20.10.10. We will update this issue as and when more information is available.

[Resolved] Known Issue: Deluge 2.0.4

Tue, 14 Dec 2021 14:00:00 +0000

Version 2.0.5 has been released to resolve this issue.

An upstream issue with deluge-web in version 2.0.4 has broken the deluge webui for users. Please roll back to the version-2.0.3-2201906121747ubuntu18.04.1 tag until a fix is published.

[Resolved] Known Issue: Paperless-ng

Mon, 26 Jul 2021 00:00:00 +0000

The initial release of our paperless-ng container did not correctly map the contents of /config with the config mount point. We are pushing an update to correct this issue, however, users will need to manually copy out their configuration files or else there will be data loss. You copy out all necessary files by running the following command:

docker cp paperless-ng:/app/paperless/data/db.sqlite3 .

This will copy the existing database to your current working directory. You can then safely place this file into the /config mount of paperless-ng and safely update.

[Resolved] Known Issue: Swag 1.15.0

Sat, 29 May 2021 00:00:00 +0000

Version 1.16 has been released to resolve this issue.

An upstream issue with certbot has broken some of the DNS validation plugins used by swag. If you are affected by this issue, please roll back to version-1.14.0 until 1.16 is released.

[Resolved] Known Issue: Unifi Controller v6.2.23

Sat, 08 May 2021 00:00:00 +0000

Ubiquiti have released v6.2.25 to resolve the issues with their original broken release.

Ubiquiti have pulled the v6.2.23 update for their Unifi Controller software due to issues with upgrading from older versions. If you have already updated your container image you will need to pull the re-released v6.1.71 and restore your config from a backup.