[Feature] Volume Shortcuts and k3d-managed volumes #916
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Added
--volume/-v
flag that k3d automatically expandsk3s-storage
->/var/lib/rancher/k3s/storage
k3s-manifests
->/var/lib/rancher/k3s/server/manifests
k3s-manifests-custom
->/var/lib/rancher/k3s/server/manifests/custom
(not K3s default: this is just some sub-directory inside the auto-deploy manifests directory which will also be parsed)k3s-containerd
->/var/lib/rancher/k3s/agent/etc/containerd/config.toml
(use with caution, K3s generates this file!)k3s-containerd-tmpl
->/var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl
(used by K3s to generate the real config above)k3s-registry-config
->/etc/rancher/k3s/registries.yaml
(or just use--registry-config
)k3d-
prefix will now be created and managed byk3d
Links
fixes #905