I have a lot of issues with AI in general, but frankly the biggest, most immediate one is that I reeeally hate when tech pretends to be human. Like search engines giving me a seventh grader's essay before the actual one-word answer I was looking for. Or the uncanny valley voice at the drive-thru speaker saying "great choice!" to everything I order. Or the AI on shopping websites saying "I'd recommend this model..." Etc etc.

There's just something so strange and uncomfortable to me about a thing that we all know is not a person pretending to be one; feels like someone telling a lie directly to my face, and I know they're lying, and they know they're lying, but I'm supposed to.. appreciate it? For some reason?

But a lot of people I know actually prefer it. They'll ask ChatGPT something—even something that has a simple, definitive answer that doesn't really need further explanation—rather than just looking it up on a search engine. I'm just curious what the difference in psychology is between us. And I'm wondering if maybe it's actually just a me problem; I mean, I hated Jeeves too, and he seemed pretty well-liked back in the day.

Full disclosure: I'm very new and very dumb. So. Bear that in mind.

I'm running Docker on Ubuntu Server 24.04 LTS. I installed it according to the official directions provided by Docker. The container example I'll refer to here is Beets, but same happens on Calibre Web Automated and a couple other containers I tried.

Basically, from within the container I can't ping google. This:

docker exec -it beets ping -c 3 google.com

returns:

PING google.com (142.250.113.138): 56 data bytes google.com ping statistics: 3 packets transmitted, 0 packets received, 100% packet loss

So, in Beets case, it can't access musicbrainz to do.. well, anything it's built to do, because it (and any other container I run) doesn't seem to be able to access the internet? Idk.

I've tried a whole bunch of stuff at this point (not really knowing what any of it means, mind you) and nothing has worked. I've checked /etc/resolved.conf, which just lists 127.0.0.53, which is apparently some sort of systemd DNS cache? Ngl, I don't really know what that means, but a potential solution I read was to override it by editing /etc/docker/daemon.json to include something like dns: [8.8.4.4, 8.8.8.8] (I don't recall the exact syntax, sorry). Anyway, that was even worse, because running the ping from inside the container then didn't resolve an IP for google at all and just said "bad address". I tried making a user-defined bridge, which output the exact same as above: 100% packet loss. I tried rebuilding the iptables, nothing. Directing containers to a network in the compose yml, restarting containers, restarting docker, rebooting. Idk.

Only thing that seems to work is adding network_mode: "host" to the container's compose yml, which... I mean, if that's the solution that works, that's what I'll do. But I'm wondering what exactly is going wrong otherwise, and if I can fix it.

Any help greatly appreciated.

I'm pretty new to self-hosting in general, so I'm sorry if I'm not using correct terminology or if this is a dumb question.

I did a big archival project last year, and ripped all 700 or so DVDs/Blu-rays I own. Ngl, I had originally planned on just having them all in a big media folder and picking out whatever I wanted to watch that way. Fortunately, I discovered Jellyfin, and went with that instead.

So I bought a mini pc to run Ubuntu server on, and I just installed Jellyfin directly there. Eventually I decided to try hosting a few other services (like Home Assistant and BookLore (R.I.P.)), which I did through Docker.

So I'm wondering, should I be running Jellyfin through Docker as well? Are there advantages to running Jellyfin through Docker as opposed to installed directly on the server? Would transitioning my Jellyfin instance to Docker be a complicated process (bearing in mind that I'm new and dumb)?

Thanks for any assistance.