Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Kubernetes examples with Docker socket #1991

Closed
wants to merge 1 commit into from

Conversation

afbjorklund
Copy link
Member

Some users are expecting to run both "Docker" and Kubernetes

Uses the regular Ubuntu system packages, for the installation

An alternative is to use Kubernetes-in-Docker, or even two VMs...

But then you can't share images between the two environments.


Experiment for Podman Desktop, possibly too bloated for upstream?

It's a merge between k8s.yaml and docker-rootful/podman-rootful

Nobody uses the podman-remote client, so show docker instead.

@AkihiroSuda
Copy link
Member

AkihiroSuda commented Nov 6, 2023

We have too many yamls now, maybe we should consider to support parameterizing?

Probably via limactl create --env

@afbjorklund

This comment was marked as off-topic.

Some users are expecting to run both "Docker" and Kubernetes

Uses the regular Ubuntu system packages, for the installation

Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
@jandubois
Copy link
Member

The k3s template is much shorter.

You can just copy the k3s provisioning script into the docker template and add the --docker option to k3s get what you want... 😸

curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--docker" sh -

@afbjorklund
Copy link
Member Author

Yeah, but the script is deprecated and only supports GCE (it does not even use kubeadm).

https://get.k8s.io

And the project prefers the interactive readme, over any automated script (only downstream).

https://docs.k8s.io (as in https://kubernetes.io/docs/setup/production-environment/ et al)

So, just use Rancher Desktop perhaps ? 😀

It is more optimized and integrated, anyway.


But it was mostly an experiment, to see how much modification was needed to add docker/podman?
And I think there wasn't much unexpected, mostly just to install the package and forward the socket.

It is unlikely that Podman Desktop will use something else than kind (kubernetes-in-podman), anyway...
Just that the kind project does not want to support cri-o, so that means they have to run with containerd.

It would be possible to add a CRI-O installation to CoreOS, but then it competes with OpenShift Local...
So that is also unlikely to happen. And now their main focus is on Compose, not actually on Kubernetes.

Most likely outcome is that I will just close these, and run with the regular Lima containerd-only clusters.
It would have been possible to use the CLI, but not if you only support the legacy API (not even ssh://).

The feature will be more of a "DIY" / edit.

If there is a unix socket, the GUI can use it?

@afbjorklund
Copy link
Member Author

We will leave these as downstream (from Lima), as some example of DYI clusters (adding on k8s.yaml).

The initial use case was Podman Desktop, which divides workflow between "containers" and "Kubernetes".

But it will pursue some path of sharing storage between the guest and the kubernetes-in-container node:

kubernetes/minikube#17415 (comment)


If you don't need access to the Legacy Docker socket, then you could just run nerdctl.lima out-of-the-box...

Like is done in Rancher Desktop, or Finch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants