> I am way more comfortable managing a system that is k3s rather than something that is still using tmux that gets wiped every reboot.

Thoughts on Tmux-resurrect[1] , it can even resurrect programs running inside of it as well. It feels like it can as such reduce complexity from something like k3s back to tmux. What are your thoughts on it?

[1]:https://github.com/tmux-plugins/tmux-resurrect?tab=readme-ov...

▲

kachapopopow a day ago | parent [-]

I had it break enough times to where I just don't bother.

▲

udev4096 2 hours ago | parent | next [-]

Skill issue. It works just fine

▲

Imustaskforhelp a day ago | parent | prev [-]

Well firstly I would love to know more about your workflow where it actually broke etc. because I feel like tmux-ressurect team could help or something for sure.

I haven't used the tool itself so I am curious as I was thinking of a similar workflow as well sometime ago

Now please answer the above questions but also I am going to assume that you are right about tmux-ressurect, even then there are other ways of doing the same thing as well.

https://www.baeldung.com/linux/process-save-restore

This mentions either Criu if you want a process to persist after a shutdown, or the shutdown utility's flags if you want to temporarily do it.

I have played around with Criu and docker, docker can even use criu with things like docker checkpoint and I have played with that as well (I used it to shutdown mid compression of a large file and recontinue compression exactly from where I left)

What are your thoughts on using criu+docker/criu + termux, I think that it itself might be an easier thing than k3s for your workflow.

Plus, I have seen some people mention vps where they are running the processes for 300 days or even more without a single shutdown iirc and I feel like modern VPS providers are insanely good at uptime, even more so than sometimes cloud providers.

	▲	kachapopopow 4 hours ago \| parent [-]
		failure scales exponentially with servers due to design limitations even using tmux resurrect on my personal machine I've had it fail to resurrect anything again - lack of documentation and loosy tmux resurrect state is not what I want to go thru when working in unfamilar environments why are you getting downvoted docker compose also has issues but at least it is defined, again if you are managing 10+ machines docker becomes a challenge to maintain especially when you have 4 to 5 clusters, when you are familiar with kubernetes there's virtually no difference between docker tmux or raw k8s, although I heavily recommend k3s due to its ability to maintain itself.