rd VS tilt-extensions

So, please please solve this request here: https://github.com/rancher-sandbox/rancher-desktop/issues/18...

https://github.com/rancher-sandbox/rancher-desktop/releases

Then in Rancher Desktop you enable WSL integration as shown here:

If using rancher desktop: https://docs.rancherdesktop.io/tutorials/working-with-images/ https://github.com/rancher-sandbox/rancher-desktop/issues/952

> docker desktop is pretty dead now that it's got restrictive licensing etc...

It would probably be nice to hear more about why you think this is! I've certainly heard of some having to move away from Docker Desktop.

However, at the scale where you need a license (250 employees or 10 million $ in annual revenue) it's not quite as big of an issue, especially at their current pricing per seat: https://www.docker.com/pricing/

> stick to standard open source tools like Colima etc...

Sticking to open source is a great idea!

I think mentioning that Colima runs on macOS and Linux only at the moment is also a good idea: https://github.com/abiosoft/colima

A large market share of the Docker Desktop installs are Windows in particular (since it's "the one way" how most install Docker nowadays, as opposed to not really needing a GUI or the supporting tools on Linux).

In another comment I mentioned Podman Desktop as a mostly viable alternative: https://github.com/containers/podman-desktop

Then there's also Rancher Desktop as well: https://github.com/rancher-sandbox/rancher-desktop

Regardless, it's nice to see reputable orgs behind the open source projects as well, which gives a bit more credence to their chances of surviving for the years to come.

Great, then can you speak to whether rancher-desktop supports the "--platform" argument to "run" the same way that finch does?

I wouldn't mind answering it myself, but it looks like rancher-desktop is an electron something or other: https://github.com/rancher-sandbox/rancher-desktop/blob/v1.6... and even downloading the 500MB release zip shows that there's `Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl` hidden in it, but I'm a distrustful sort and I don't want to crawl through unlimited lines of typescript to find out what this is going to do to my system

Maybe it's just that I'm not the right audience for this, since I am the polar opposite of "some gui fanciness," as I came up through the docker-machine universe, and now colima, and thus have a lot more comfort debugging CLI tooling when something inevitably goes toes up

The first is the load function which loads Tilt extensions. It's a way to expand the tool's features, and several are available. Here we are using docker_build_with_restart, which will update the container running inside our Kubernetes cluster.

This is the central viewport into manual resource control and environment enhancement through the open-source extensions for Tilt.

argocd for cd Tilt

Recently, I found Tilt [0] to be a good partner of mine to run "all services locally". It can be compared to "webpack (live-reloading, a lot of configuration possibilities) for backend". You want to run a bunch of services directly? Use local_resource()/local(). You have Procfile? There is procfile() function. You have docker-compose.yml with databases? You can run it too with docker_compose(). You want have Tiltfile and include them all-together? There is load(). You need some web-ui for frontend devs and a nice log browser? It is there too. You need to do some extra steps before running a service? You want to update your local cluster with newly built image on file save? No problem, tilt will do that with k8s_yaml() function. Tilt uses Titlfiles for configuration, which are written Pythonish Starlark language and you use them to run any specific logic there.

Also, I am not very lucky in having resemble 1:1 k8s cluster locally. You could be close but as long as you don't run already in cloud you will have different configuration (additional annotations, various quirks that do not exist in kind/k3s but they are on GCP). However, making dedicated dev environments in the cloud might be very costly and incur a lot of additional tinkering.

[0]: https://tilt.dev/

If `host` means your production/staging hosts or whatever, you should get out of that habit now. Look into something like tilt.dev or telepresence.io or any number of other solutions that help solve this issue. Doing it directly on any host is just a recipe for bad habits and disaster.

The article doesn't mention k3d (https://k3d.io/) which is a variant of k3s that runs in docker (rather than a VM) - very nice for k8s dev/test on developer workstations.

It integrates very nicely with https://tilt.dev/ also (another very useful tool for k8s related dev/test).

If this is an issue during development then you can use something like tilt with docker-compose to directly copy modified source inside container and incrementally build it. https://tilt.dev/

I'd add Tilt

Tilt

Along similar lines, how about comparing Devspace to [Tilt](https://tilt.dev/)?