certificates VS podman-compose

I've been doing this for a while with SmallStep CA: https://github.com/smallstep/certificates

It's a bit of a pain to load a cert onto every device (easier with stuff like Ansible if you have a bunch of linux devices), but manageable. And it lets me do proper trusted TLS for a lot of stuff that would otherwise be self-signed.

One thing I recommend is to add X509v3 Name Constraints extensions to your root CA if you go down this path. It prevents the CA from being abused to MITM you for other URLS (at least for browsers/clients that respect names constraints)

```

You can roll your own with https://github.com/smallstep/certificates. We maintain major open source projects and contribute a lot to other projects. I don’t think that means everything we do has to be open source. Sorry this one wasn’t. Doing this in pure open source would be a book, not a blog post.

Love Let’s Encrypt — we’re sponsors — but using them for WiFi is a terrible idea. You need internal PKI for WiFi.

letsencrypt was always about moving the public internet off of http, it doesn't really make sense to use it throughout your internal network. but if you really want TLS and ACME for auto renewal, other solutions are available: https://github.com/smallstep/certificates

You could try step-ca: https://github.com/smallstep/certificates. There’s an OIDC provisioner for SSO and you can sign (short-lived) SSH certificates with it.

You could also check out out Step CA: https://github.com/smallstep/certificates and the accompanying CLI. It has an ACME server and other methods for requesting certificates. It can work/integrate with your existing root(s), too.

This is a lot more complicated setup but it works for me. I run a private CA called step-ca from smallstep and it provides CA and ACME endpoint. I use a .home domain. The trick is the validation for non-http devices which is typically the DNS-01 challenge. For this, I have unbound in pfsense setup to work with acme-dns so I can keep everything internal. Again its complicated but if your learning cyber security it might help get a handle on all things TLS. Btw way behind the scenes I think the ACME plugin is really just running acme.sh bash script which is really good. Final reminder as other have stated. Private CA is great but you need to distro the roots and intermediates out to your clients for trust. If all your trying to do is have an https web gui for pfsense from one device its pretty easy.

Just a little heads up https://smallstep.com/certificates/

Step-ca: Not web based, but the CLI is pretty user friendly: https://smallstep.com/certificates/

Podman (via podman-compose),

Source code for the feature is here if you care to inspect it:

https://github.com/containers/podman-compose/blob/bce40c2db3...

Admittedly, I'm still on podman 4.3.1, but I dont' see any reason why this would stop working in later versions of podman.

Can someone link me to what Compose means in this context? Google takes me to https://github.com/containers/podman-compose but I just wanna make sure that's what they are talking about.

🛑 Docker Desktop is free for personal use but requires a paid subscription for enterprises. A free open source alternative is Podman and Podman Compose which uses the same core syntax as the Docker tools and can be used as a near drop-in replacement.

I’m dumb. When I wrote the article it was late. Docker-Compose really was a game changer.

Yea Podman compose exists. I’ll add a section about docker compose to it in an update.

https://github.com/containers/podman-compose

From googling this error I've come across a few different threads but I haven't gained any success. Firstly I found this github thread which doesn't reference my error but still seems related. I followed the "sudo podman-compose systemd --action create-unit" and "podman-compose systemd -a register -f myfile.yml" minus the -f flag as it wouldnt run with that. This indeed created a [email protected] file, but its created in the /etc/systemd/user directory rather than /etc/systemd/system which raises an issue as I'm having to run these two containers as root. I try registering the podman-compose@torrent but I'm told the service doesnt exist. Running it as user I'm told it failed to connect to bus: no medium found. So I basically reached a dead end there.

Have a look at Podman Compose

You can also use podman-compose for the orchestration https://github.com/containers/podman-compose