d.rymcg.tech VS mrsk

> What if the docker daemon is on a storage server and the host volume of /stuff contains, say, 10 terabytes of photo album content?

In this extreme example I think probably a bind mount might make sense, especially if the files are already there. But the named volume would just be stored in /var/lib/docker/volumes/some-volume-name, so as long as that /var/lib has 10TB I don't see the problem.

I can use my sftp container [1] to be able to sftp directly into a volume, but I've not yet transferred 10TB with it :)

[1] https://github.com/EnigmaCurry/d.rymcg.tech/tree/master/sftp

yea, I've mostly come to the same conclusion, podman is a hobby, I can see its potention so I actively track it, but I I do mostly do stuff with vanilla docker and docker-compose, for single one-off installs, and k8s for bigger distributed stuff, either in a VM locally, or on a DigitalOcean dropet(s). I've been collecting my compose files [1]

[1] https://github.com/EnigmaCurry/d.rymcg.tech

Here we'll deploy Anycable wih MRSK.

Honestly these days I am leaning towards this approach: https://github.com/mrsked/mrsk/

It's all just docker.

Did you consider MRSK[1], k3s[2], or dokku[3]? They are all significantly simpler to operate than Kubernetes, curious to hear your take.

[1] https://github.com/mrsked/mrsk

https://github.com/mrsked/mrsk/pull/159 Closed PR about --cache-to option in MRSK

Yes, that thing with the setup is misleading in the docs. I'll make a PR now. There's this issue about it: https://github.com/mrsked/mrsk/issues/301

god or bad, dhh is doing noise and people know about rails. just look at there https://github.com/mrsked/mrsk

I don't think there's a writeup out there, but mrsk just uses docker under the hood. So, if you have a CMD in your Dockerfile, it will use that.

If you have an image that can run multiple things, like a rails app that can run the app process for web traffic by default, but it can also run job workers with the right command, you can provide the cmd in the mrsk config. You can see this in the jobs role in the example: https://github.com/mrsked/mrsk#using-different-roles-for-ser....

You may want to checkout MRSK if you are going to be using docker compose in production on a single VPS https://github.com/mrsked/mrsk

"MRSK basically is Capistrano for Containers, without the need to carefully prepare servers in advance" https://github.com/mrsked/mrsk

https://github.com/mrsked/mrsk might be interesting to you.