Clarify in k3s documentation that a registry is required about dokku HOT 4 OPEN

The k3s scheduler requires a registry, full stop. K3s uses containers, which doesn't have access to your local docker images, so attempting to deploy without a configured registry will fail.

from dokku.

Thanks for clarifying @josegonzalez

I was able to get it to work by setting the following options:

docker login ....
dokku registry:set --global server $server
dokku registry:set --global image-repo-template "$namespace/{{ .AppName }}"
dokku registry:set --global push-on-release true

This wasn't clear in the docs and took some time to figure out all the steps to get it working.
I'll see if I can maybe create a PR to update the k3s docs with this information in the following weeks.

Edit: I actually just found this tutorial: https://dokku.com/tutorials/other/deploying-to-k3s/. Might just add a link to this tutorial from the docs page

from dokku.

Also on a separate note, is there a way to link external services when using k3s? Like MySQL or Postgres?
Currently mysql:create creates a container on the local docker instance, which the k3s pod then don't have access to. Is there an alternative way to use the k3s scheduler when creating services through plugins?

from dokku.

The scheduler plugins do not start services on k3s, and I don't have any current plans to enable that sort of functionality (as you can imagine, things get much more complicated when making something highly available).

I recommend looking at the official helm charts/operators for the datastores you're looking at. Bitnami also has some decent helm charts that might be useful to look into.

from dokku.