Hexbear user since a couple days of their launch before federation was a thing. The instances you’re knocking are older than every other instance, and the defeds were typically preemptive to the point where people on other instances usually have no fucking clue what they’re talking about.

Always makes this stuff bewildering, but we’ll be here with you or not.

Well, had one go in an almost brand new to me car over a set of tracks in the dead of winter as a naive kid and didn’t figure it out for quite a while. 😛

Even went autocrossing with it like that and couldn’t figure out why the hell I was sliding into every corner. Was probably losing about 3 seconds over each run it was so bad.

We have card payments at the pumps, and the garbage can thing was very much a weird NYC thing.

I don’t think the migration will be that awful going from Linux to Linux container? I just gave up and nuked it going from Windows to a Linux container, but that was after hours of playing whack-a-mole with Windows -> Linux path issues.

The main thing is you’ll probably want to mount your media location as a volume in docker using the same location as it was on bare metal, as otherwise I think you’ll need to fix all those paths in Jellyfin’s DBs. Otherwise you’ll need to locate Jellyfin’s config/etc directory and mount it in docker with the appropriate binds, and while doing that you’ll probably want to move it to a spot that’s more appropriate for container config storage.

An additional thing is that the container will need to be explicitly given access to your GPU for transcoding if needed, but that changes with your system and is just part of Jellyfin docker setup.