How to add Kubernetes apps repository

Incus
1

What I’m trying:

$ incus remote add kubernetes https://kubernetes.io --protocol=oci
$ incus launch kubernetes:nginx MyApp --console
Launching MyApp
Error: Failed instance creation: Failed to run: skopeo --insecure-policy inspect docker://kubernetes.io/nginx --no-tags: exit status 1 (time="2026-08-13T11:02:35+02:00" level=fatal msg="Error parsing image name)

2

Is there an OCI image registry at kubernetes.io?

3

@abiosoft I have no idea. Trying with k8s.io says the same error, but I don’t know any path to trust k8s.io address.

4

In that case, you would need to first figure out the public url for the OCI image registry, then you can add it as a remote in Incus.

5

default registry for kubernetes is docker.io

6

@xlmnxp do you mean there is no Kubernetes apps repository, and it’s only an interface of Docker with different name?

7

What do you mean when you say “kubernetes apps”? Do you have a particular “app” in mind?

  • Apps that you can run under Kubernetes? Those are just docker containers. Apps aren’t written specifically for kubernetes.[^1] Therefore, they are distributed at the places you normally find docker containers, like docker.io and quay.io. There’s no different name, because they don’t know or care whether you plan to deploy these containers with docker engine or kubernetes or incus-compose, swarm, nomad, or any other tool.
  • A way to deploy Kubernetes itself? Kubernetes isn’t normally deployed inside docker containers. [^2]

[^1] There are layers on top of kubernetes, such as helm, to assist with creating the resources to deploy a collection of related OCI containers. But they’re still just deploying regular OCI images. And helm charts themselves are distributed using a completely separate mechanism.
[^2] Although there is KIND (kubernetes in docker), you didn’t mention that specifically, so I don’t think that’s what you mean. In any case, KIND is usually used just for integration testing, not real deployment of applications.