Track Error; Something went wrong decoding the track. (OpenJDK11)

[FaNt4zMa]

Describe the bug Pretty often I get an error saying something went wrong decoding the track. I'd say 50% of songs I'd play would just stop randomly. So it got me thinking, maybe it has to do with the java version itself because, on Red's website, they recommend openjdk17-jre and I see that the dockerfile installs openjdk11... I'm pretty novice with docker still and don't know how to modify a dockerfile and build my own container, so if you could update the dockerfile to install 17, that would be very nice and maybe fix the problem :)

Run command

services:
    red-discordbot:
       image: phasecorex/red-discordbot
       container_name: red-discordbot
       env_file: stack.env
       environment:
            - TOKEN=$TOKEN
            - OWNER=$OWNER
            - PREFIX=$PREFIX
            - TZ=$TZ
            - PUID=$PUID
       volumes:
            - /home/fantaz/Tools/Red Discord Bot/data:/data
       restart: unless-stopped

Environment info: OS: linux x86_64 Ubuntu 22.04.4 LTS Kernel: 5.15.0-113-generic Docker Version: 27.0.3 Portainer Version: 2.20.3 CPU: i3 380M 2.53GHz RAM: 4GB DDR3 1067MHz

Additional context

[PhasecoreX]

Yeah, for the longest time they recommended Java 11, but I guess at some point (probably a while ago) they switched to 17. I'm not sure if it will fix this problem, as that's usually caused by YouTube doing weird stuff and changing things that requires lavalink to be updated, but I do want to update the base container to Debian 12 and Java 17, so I'll leave this issue open.

[FaNt4zMa]

Cool. Once you do, let me know and I'll do some testing on my end. I may try playing with the Niceness value since my machine is pretty low powered and also running 20+ other containers, one of which was another music bot I was trying out but this one didn't have any issue (tho the sound quality was slightly worst in the bass freq, so I prefer Red in that regard)

[PhasecoreX]

Alright, latest update is now using Debian 12 and OpenJDK 17, as recommended by the official install docs. Seems like everything is working fine and I didn't break anything, which is cool. I still get "Something broke when playing the track" errors though, but that is Lavalink related and not a container issue, so will have to wait on a Red update to that.

[FaNt4zMa]

That's odd, the other music bot I was trying out also uses lavalink and during my testing rarely ever crashed, if at all..

[PhasecoreX]

It could be that the other bot uses the stock Lavalink, whereas Red uses a custom Lavalink version. Not sure. Red is also doing a bit more than just music stuff, but that shouldn't matter too much I'd think.