You have trouble getting Docker to auto-start on Windows? I thought that was the default behavior…
Comment on Latest success Jellyfin rocks!
JRaccoon@discuss.tchncs.de 1 week ago
Asking out of curiosity: is there a specific reason you’re running Windows on your server? I used to do the same on my home servers because that’s what we used to have at work, and I wanted to learn and test some stuff. But it was a difficult road, to put it mildly. Simple things, like getting Docker autostart on boot seemed almost impossible. At some point I just gave up and switched to Linux.
mic_check_one_two@lemmy.dbzer0.com 5 days ago
- JRaccoon@discuss.tchncs.de 5 days ago
It works great when you log in as a user like you normally would on a Windows pc. But on a server you want it to run as a service, starting automatically in the background and/or being managed by the failover cluster without requiring a user to log in.
The solution back then was to use
netplwizautologon. Obviously a hack and bad for security, but fine for a homelab. After googling it now, it looks like some other “solutions” are documented in the GitHub issue about this.
I use Windows Server because that’s what I know. Though I am curious to learn other OSes when I have more time. I don’t use docker so that’s really not a problem for now.