Here’s how to use synowebapi for stopping (and starting) projects in Container Manager on a Synology NAS.

My home DNS is a bit of a mess, so I want to install CoreDNS on my Synology NAS to tidy it all up. I’ll run it in a container.

In part 1, and part 2, I’d got Forgejo running on my Synology NAS, with HTTPS and SSH access. It’s not being backed up (or restored); let’s fix that.

In part 1, I’d got Forgejo running on my Synology NAS, but SSH access wasn’t working properly. In this part, I’m going to fix that by using HAProxy.

I want to install Forgejo on my Synology NAS. I’m going to attach it to the macvlan network I createed yesterday. I’m not going to use Synology’s built-in Web Portal (reverse proxy thing). Here’s how I did it.

In the previous post, I investigated using Docker with the macvlan network driver, to allow containers to have unique external IP addresses. This is the follow-up post where I apply the changes to my Synology NAS.

Pushing a simple node.js-based image to my private docker registry failed.

The default option for persistent volumes on k3s is local-path, which provisions (on-demand) the storage on the node’s local disk. This has the unfortunate side-effect that the container is now tied to that particular node.

I wanted to get Erlang running on my Synology NAS, for various reasons, and was struggling with the cross compiler.