Inter-container communication is different. At least with docker which I have more experience with, but they’re similar. Try using the name of your container in your proxy config rather than the external host name.

Are these running on the same server? You haven’t given a lot of information here. Communication between containers is different:

https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/assembly_communicating-among-containers_building-running-and-managing-containers#proc_communicating-between-a-container-and-an-application_assembly_communicating-among-containers

“bare metal” does not mean “outside of a container”. Just say “outside of a container”.

It’s a losing battle, but I’ll fight it anyway.

If you’re just pulling “latest” then docker will fetch the latest when it starts. You can pin to a version tag if you want to keep it stable.

Yeah, you can’t. There is no guarantee that clients will use dns servers in any particular order.

“Linux doesn’t boot”

Maybe begin with any information at all then if you want this to be helpful to others?

Yeah, it’s really not called out in the docs. I found out the same way.

I freed 50gb by running ‘docker system prune’…

Has it?

https://blog.mozilla.org/en/products/firefox/update-on-terms-of-use/

Ah - I get that. You have my sympathies.

A personal project like that would be a great way to train/get experience then. But do realize that it becomes a lot more complicated once you have people other than yourself relying on your application. Suddenly up-time becomes very important and up-time is hard. End-users, even friendly ones, get very frustrated when you say “try now please” a lot. They’ll just stop using it.

HIPAA (not hippa) is not even remotely applicable.

Cheap and easy are in opposition here. Which matters more? There are symptom and medication apps already that would be easy and available right now. And you don’t need to do tech support for family.

The color-management Wayland extension is enough for entertainment purposes like games and movies. However, it is not enough for professional color management needs including photo editing and print preview.

12 years…

Actual Linux news rather than “which distro should I use for gaming and bit torrents?”

Sometimes you gotta let people try to resolve things on their own first.

Sounds like something is broken.

As someone who has seen almost EVERY kernel bugfix and security issue for the past 15+ years (well hopefully all of them end up in the stable trees, we do miss some at times when maintainers/developers forget to mark them as bugfixes), and who sees EVERY kernel CVE issued, I think I can speak on this topic.

The majority of bugs (quantity, not quality/severity) we have are due to the stupid little corner cases in C that are totally gone in Rust. Things like simple overwrites of memory (not that rust can catch all of these by far), error path cleanups, forgetting to check error values, and use-after-free mistakes. That’s why I’m wanting to see Rust get into the kernel, these types of issues just go away, allowing developers and maintainers more time to focus on the REAL bugs that happen (i.e. logic issues, race conditions, etc.)

I assume you’ve configured it for “single” mode?

Don’t be shitty.

You need the same source code, the same exact build tools, the same exact libraries that it depends on, and the same exact OS. Additionally every single build has to be reproducible - so not including in its output, say, the build date/time or any information about the host that built it. Now you need to repeat that for thousands of packages.

I believe it’s less about the packaging system and more about the build system. You’re building source code from thousands of individual projects, getting a reproducible output is difficult if, for example, some library embeds the build date/time in its output.

Oof, awk…

I consider myself to be very cli proficient, but I’ve never understood awk.