-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
New package: k3d-4.4.7 #32349
New package: k3d-4.4.7 #32349
Conversation
# to pull. incorrect strings here result in cluster creation | ||
# failures+rollbacks. | ||
go_ldflags="-X github.com/rancher/k3d/v4/version.Version=v${version}" | ||
depends="docker" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could it work with podman?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No: k3d-io/k3d#84
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it will possibly arrive, I'd rather this not depend on docker
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I can tell in the thread, this isn't being actively worked on, there's no ETA of when or if it may ever get worked on, and for that matter, got punted from a milestone to generic "backlog".
It looks safe to assume that at least for the near term (I'd guess at least 6mo), this is a Docker-only tool, and thus should depend on docker
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly I want to keep flexibility. We shouldn't have this tool be responsible for bringing in docker to people's system, otherwise if anything changes we'll have to figure out a fix, since docker
will become an orphan package (in some situations).
k3d wound up not working for what I needed, and I moved over to |
Since no one's else expressed interest, and maintaining a package you don't use can be tiring and harder than it needs to be, i think it's ok to close this. |
Works for me. Thanks for the feedback on this regardless! |
General
Have the results of the proposed changes been tested?
I'm not a master of k3d by any means - I'm using it as a cheap playground to test out Tilt at work (which I might also package today). That said, I successfully created a simple cluster with
k3d cluster create myclusternamehere
using this package, so it seems alright.