one-click-apps VS nerdctl

There are images for it on Docker Hub. I wrote a Redmine deployment spec for the PaaS I use (Caprover) for my personal app server. It’s a lot like Docker Compose, but as it actually functions using the Docker API, some Compose features are unavailable. If you’re familiar with Compose, you should be able to easily adapt this Caprover template: https://github.com/caprover/one-click-apps/blob/aaa12a4f37f7...

https://github.com/caprover/caprover https://github.com/caprover/one-click-apps

> Which One-Click App are you using? I looked over their list, but couldn't find the Docker Registry. Thanks!

I'm not sure about them, but Nexus might fit the bill from that list: https://github.com/caprover/one-click-apps/blob/master/publi...

It's what I'm using for myself (though with just Docker Swarm + Apache2, without Caprover) and has worked well for years.

Note that mattermost by default phones home to a spyware analytics service even when you selfhost it. The env vars for disabling it are hidden/undocumented.

Copy the diagnostics/securityalert env vars from here, as well as the sed lines:

https://github.com/caprover/one-click-apps/blob/master/publi...

What about the docker-cli? colima also ships with a docker-compatible cli to interact with containerd called nerdctl. We can execute the same docker cli commands like:

Using nerdctl: https://github.com/containerd/nerdctl

I'd really disagree that compose files are somehow one-shot, or blindly modified. To the contrary, really, we have them checked in with the source code. Upon deployment to the cluster, the (running) services will be intelligently updated or replaced (in a rolling manner, causing zero downtime). LXC might be more elegant, but I have no idea what simple, file-based format I could use to let engineers describe the environment their app should run in without compose.

I need something that even junior devs can start up with a single command, that can be placed in the VCS along with the code, and that will not require deep Linux knowledge to get running. Open for suggestions here, really.

Now since Kubernetes works off of containerd I'll be taking a different approach on handling container builds by using nerdctl and the buildkit that comes bundled with it. I'll do this on the amd64 control plane node since it's beefier than my Raspberry Pi workers for handling builds and build related services. Go ahead and download and unpack the latest nerdctl release as of writing (make sure to check the release page in case there's a new one):

That's why nerdctl, their cli binary, is so well named.

Well, it is indeed a good option. However, containerd is a good alternative that is growing even among developers. Please see: https://github.com/containerd/nerdctl

Nerdctl/containerd has IPFS support :)

https://github.com/containerd/nerdctl/blob/main/docs/ipfs.md

nerdctl supports IPFS for both image pulling and pushing, including encrypted images and eStargz lazy pulling. For building, the current method is a locally hosted translator so that the traditional pulls can be converted to work over IPFS. They even have docs on running it on k8s node, though if my reading is correct this isn't exactly a cloud native approach (running systemd services on each node...).