Unfortunately fresh containers enter a restart loop because Roon have changed the URL of the server build archive. The previous location now returns a 301 Moved Permanently, but the curl usage in run.sh is missing the -L option required for it to follow the redirect. The HTML returned from the server for the 301 is piped to tar instead, resulting in the error bzip2: (stdin) is not a bzip2 file appearing in the logs.
The change made by Roon seems to have been to move builds to download.roonlabs.net from download.roonlabs.com, so I've successfully worked around this by overriding ROON_SERVER_URL to http://download.roonlabs.net/builds/RoonServer_linuxx64.tar.bz2.
Hello, thank you for this image.
Unfortunately fresh containers enter a restart loop because Roon have changed the URL of the server build archive. The previous location now returns a 301 Moved Permanently, but the
curlusage inrun.shis missing the-Loption required for it to follow the redirect. The HTML returned from the server for the 301 is piped totarinstead, resulting in the errorbzip2: (stdin) is not a bzip2 fileappearing in the logs.Discussion thread I was able to find on this topic: https://community.roonlabs.com/t/roonbridge-fails-to-update-with-bzip2-stdin-is-not-a-bzip2-file-error/196153
The change made by Roon seems to have been to move builds to
download.roonlabs.netfromdownload.roonlabs.com, so I've successfully worked around this by overridingROON_SERVER_URLtohttp://download.roonlabs.net/builds/RoonServer_linuxx64.tar.bz2.