Ive actually been personally moving away from kubernetes for this kind of deployment and I am a big fan of using ansible to deploy containers using podman systemd units, you have a series of systemd .container files like the one below
[Unit]
Description=Loki
[Container]
Image=docker.io/grafana/loki:3.4.1
# Use volume and network defined below
Volume=/mnt/loki-config:/mnt/config
Volume=loki-tmp:/tmp/loki
PublishPort=3100:3100
AutoUpdate=registry
[Service]
Restart=always
TimeoutStartSec=900
[Install]
# Start by default on boot
WantedBy=multi-user.target default.target
You use ansible to write these into your /etc/containers/systemd/ folder. Example the file above gets written as /etc/containers/systemd/loki.container.
Your ansible script will then call systemctl daemon-reload and then you can systemctl start loki to finish the example
During my expirementation with some of these self hosted llms, I was attempting some jailbreaks and other things and thought would this be any good at ERP?
Only if youve never been with another human being.
Its a full linux os, so you can do literally anything that can be done with existing tooling. For example, I have syncthing installed on mine so i just have to drop files into a folder on another computer of mine and they show up.
The software folks have put together a decent experience in the last few years and its rather nice out of the box.
I really love the byline here. "Kindest view of one another". Seething rage at the bullshittery these "web3" fuckheads keep producing certainly isn't kind for sure.
This reminds me of when I was planning out a tubular bells project. there is an amount of crankery around various notes and I came across a series of videos about the various Cs and their use in healing or chakra alignment.
When i went to buy some tuning forks I noted some more weird mysticism, but hey at least they produced a nice set of C notes.
I think the gap you have is in understanding that Podman Compose was meant to line up with the limitations of docker's compose, but technically is more capable.
Quadlet files let you do more complex workflows like deploying multiple copies of a service in your deployment that regular compose doesn't, while not running full kube.
The use I have is that I have something deployed in compose right now that I'd like to scale up on the box since i have the capacity for it, but dont want to deal with a full kube setup or the politic
Personally I've converted most of my single node k3s to using quadlet files instead as its less fragile. I absolutely deploy single containers in the quadlet. They show up in journalctl and the ergonomics are great.
Man this company has had some really interesting ideas and then the execution always falters.
I was still subscribed when the first eve-fps crossover they attempted. it seemed great and then for whatever reason a console exclusive with a subscription fee ontop. They didnt get the numbers they were planning for and the whole thing just died on the vine.
They've had some neat tech here and there and the whole experience is great for building out your psychopathy but i lost interest after the Greed Is Good phase of CCCP games started.
Ive actually been personally moving away from kubernetes for this kind of deployment and I am a big fan of using ansible to deploy containers using podman systemd units, you have a series of systemd .container files like the one below
You use ansible to write these into your /etc/containers/systemd/ folder. Example the file above gets written as /etc/containers/systemd/loki.container.
Your ansible script will then call
systemctl daemon-reloadand then you cansystemctl start lokito finish the example