mrsk VS dockerfiles

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.

https://blog.jessfraz.com/post/docker-containers-on-the-desk... is the one I remember, a bit old but still useful to see how she does it.

Seems super painful and indirected for a nebulous gain to me, but find your joy however you want I guess

Jess does some awesome stuff and this is literally what you asked for. hollywood

mildly relevant https://blog.jessfraz.com/post/docker-containers-on-the-desktop/

Some of my day-to-day software.

After knowing that saved Chrome passwords and cookies in Linux are not protected against malicious dependencies in our development environment or other apps in our system, I decided to run my core apps in Docker containers, where their data is not accessible without sudo, and a personal understanding of where stuff is being saved.

These docker containers are also an improved version of https://github.com/jessfraz/dockerfiles/

Contrary to the project above, docker-workspaces runs Chrome in a sandbox, encrypts keys with the help of an also dockerized gnome-keychain, and works in tandem with pulseaudio, so you can use wired headphones (i still need to add some dependencies for it to work with bluetooth headphones).

Thank you. As someone who uses containers a lot (even to run local programs, shout out to https://blog.jessfraz.com/post/docker-containers-on-the-desk...) this makes some sense to me.

I'm a little way into the Nix Pills document (https://nixos.org/guides/nix-pills/why-you-should-give-it-a-...) which seems to start the explanation from a place where I can understand.