k3d icon indicating copy to clipboard operation
k3d copied to clipboard

Little helper to run CNCF's k3s in Docker

Results 229 k3d issues
Sort by recently updated
recently updated
newest added

Hi, First off thank you so much for all you efforts with this project. It has been extremely helpful to me. I have a question regarding adding a node to...

question

When scripting to create k3s cluster with k3d via config file, I am not able to pass the config via `stidin` ## What did you do ```shell cat

bug

## Is your feature request related to a problem or a Pull Request No ## Scope of your request A new flag for `k3d cluster create`: `--kubeconfig-context-name=myname` ## Describe the...

enhancement

## What did you do - How was the cluster created? - `k3d cluster create mycluster --api-port myclusterhostname:6443 --network host --no-lb --k3s-arg '--disable=traefik@server:*' --k3s-arg '--disable=metrics-server@server:*' --registry-config "/home/user/config.yaml"` with "/home/user/config.yaml" as:...

bug

I have seen closed issues #366 and #206 and the discussion #478 about Longhorn and if I am correct there is still no way to use longhorn in k3d. It...

enhancement

## What did you do - Set up Rootless Podman and Podman Docker compatibility - Create a Fedora Toolbox container - Install k3d inside the container - Run `k3d cluster...

bug

The current guide at https://k3d.io/usage/guides/cuda/ is a bit out of date and doesn't work for newer OS and/or k3s versions, as reported by @vainkop. Seems like the base image should...

enhancement
help wanted
docs

This PR drains the node before stopping the container (incase of `docker stop`/`k3d cluster stop`/`k3d node stop`/system shutdown) It allows services to gracefully shutdown in this case, this is specially...

@iwilltry42 I'm seeing this issue on ubuntu when upgrading from k3d 5.3.0 to 5.4.1. I'm seeing output like: ``` INFO[0000] Importing image(s) into cluster '$CLUSTER_NAME' INFO[0000] Starting new tools node......

bug
priority/medium

When stopping a `k3d` cluster, the pods don't exit gracefully. This can cause stateful services such as `mongodb` and other databases to fail restart. To simplify, I'm describing the behavior...

bug