For development, I’d recommend going the DevContainer route, too.
I recently tried out an alternative approach successfully by running MySQL in a Quadlet-controlled container. This approach is probably better geared for running services on a continuous basis, not just during dev work.
I am… at least I am now that I got my tail out of the knot I got it into… 
I do wish commands inside the devcontainer were a little less cumbersome but it’s pretty nice.
I’m not actually running a Redis server. I’m writing a clone of Redis in Go as an exercise in learning Go, goroutines, etc. But I am running it on the same port and implementing the basic RESP commands, so I have needed the ability to run redis-cli commands inside the container where my little in-RAM database is running.
It’s possible I could use this at work, where we are getting to the point that we need some basic network caching of certain reference data, but it’s mostly for fun/educational reasons. My work is a small nonprofit that had next-to-zero modern infrastructure when I got here and I’ve been trying to get things working better since we do have a lot of public facing stuff to do our work (we mostly do foster family recruitment).
I run services using rootless quadlets. e.g.
The only issue I have had is with use of privileged ports.
Also, ptyxis does a pretty good job of opening shells in running containers.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.