It can always get worse…
Its networking is a bit hard to tweak, but I also dont find I need to most of the time. And when I do, its usually just setting the network to host and calling it done.
Are you using docker compose scripts? Backup should be easy, you have your compose scripts to configure the containers, then the scripts can easily be commited somewhere or backed up.
Data should be volume mounted into the container, and then the host disk can be backed up.
The only app that I’ve had to fight docker on is Seafile, and even that works quite well now.
There are android clients, probably one for iOS as well. If you are getting OOM killed, you need to work out what is using all your memory. The OOM killer is pretty indiscriminate, and will murder processes randomly.
Maybe keep system monitor up and keep an eye on memory usage?
Can you enable SSH, and then try SSH into the box once it hangs?
Any OOMKiller messages in dmesg/journalctl? Do you have swap space?
Nothing in the logs jumped out at me, hopefully someone else can help you.
I think you need to factor in lube costs, and once you do, it stops making financial sense.
You can have an offline gitlab/forgejo and a public github. I do most of my work against a local gitlab, and mirror up to github for anything that needs to be shared.
I have a couple of projects mirrored down to my gitlab as a backup, and they are not online, so can’t realistically be DCMAd.
Right after a new feature is also perfect time for it to get axed
Love it or hate it, Google Messages is here to stay
Oh you sweet summer child…
Looks like you need to use [
on friendica? ]
~~Take a photo of the output? First few lines are most important, but ideally all would be good. ~~
Edit: actually, dont want to crowd the kitchen, good luck!
Yup, didn’t read your comment properly, but that will also work.
Give the output of route
, maybe there is a left over route.
I’m really happy to hear that, I still have and occasionally use my steam controller, I quite liked it.
Completed stray with it and a steamlink.
Redhat were very successful with the open source, but paid support model, so it could happen.
Inertia would be hard to overcome, anyone using sales force right now is probably not gonna want to risk a newcomer.
Isnt that exactly what minikube is? Kubernetes in docker.
I’ve used docker-in-docker images, but its usually not fun.
Unless they decided to nuke all the arable land instead, lower upfront deaths, but the long term famine will get everyone.
Realistically, nuclear war is the end of everyone, its called MAD for a reason.
Container overhead is near zero. They are not virtualized or anything like that, they are just processes on your host system that are isolated. Its functionally not much more different to chroot.