There's nothing so special about weechat that it wouldn't work and you can just exec into the container and attach to tmux.
Running tmux/screen inside a container is definitely cursed, but, it works surprisingly well.
There's nothing so special about weechat that it wouldn't work and you can just exec into the container and attach to tmux.
Running tmux/screen inside a container is definitely cursed, but, it works surprisingly well.
And at that point, it may as well just be a normal Ubuntu server.
I would personally consider that a bit of an anti-pattern (I would always want to have software upgrades tied to the container) but that makes sense!
Basically 3 paths for:
- things with well-maintained upstream helm charts (checks the latest version of the helm chart and updates helmfile)
- things where I wrote a helm chart (checks for the latest container image and updates the values.yaml)
- things where there is no (reasonable) public docker image, or my own software, where I have full CI/CD to build and deploy a new container image.
Probably takes me 15 minutes a week to keep my two personal clusters fully up-to-date.
docker run -itd ubuntu:24.04
...
docker exec -it df36 /bin/bash
...
root@df365a3d2257:/# apt update
...
root@df365a3d2257:/# apt upgrade
...