Closed mgutt closed 2 years ago
There was a weird zlib bug a couple of months back that was causing that sort of thing - as I recall it was very arch and cpu dependent because it had different optimized codepaths for various combinations?
Oh, no, just been bitten by it here, it's simpler than that! The contents of the jar in the container are now:
<?xml version="1.0" encoding="utf-8"?><Error><Code>ServerBusy</Code><Message>Egress is over the account limit.
RequestId:99e83367-f01e-006d-1043-9f962e000000
Time:2022-07-24T09:53:40.2696301Z</Message></Error>
Please use the issue template and provide all of the requested information.
Honestly, it looks like it's just a broken build. Best guess is github were having transient problems and the Dockerfile couldn't download the booksonic jar. Could someone kick off a rebuild?
Yeah looks like CI failed but didn't flag properly. Have rerun the build and we'll see what happens https://ci.linuxserver.io/blue/organizations/jenkins/Docker-Pipeline-Builders%2Fdocker-booksonic-air/detail/master/172/pipeline
CI looks good this time (ignore the "broken" screenshots, it just takes too long for the UI to start) https://ci-tests.linuxserver.io/linuxserver/booksonic-air/v2201.1.0-ls62/index.html
Looks good here!
After updating the container it returns this error message
Cross Link: https://forums.unraid.net/topic/125991-docker-die-bei-mir-nicht-laufen/?do=findComment&comment=1151657