Add fixed k3d version used for docker images #566
Merged
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.
Description
As a part of #492 I discovered that the
capact env create k3ddoesn't work.capact env create k3dwas introduced, it was also the latest release.k3d-proxy:latestand it was using it instead of pulling a new one.The problematic part, was that the
k3dgo lib in version v4 was creating a docker container from thek3d-proxy:latestimage instead ofk3d-proxy:v4.4.8. Thelatesttag was selected as thegithub.com/rancher/k3d/v4/version.Versionwas not set.In the
k3d-proxy:latestimage they change the way how the config is loaded, from theenvtofilebackend (since v5 version, which is the latest one right now). This resulted in error:and from
serverlbcontainer logs:Changes proposed in this pull request:
-v=traceis usedRelated issue(s)
capact env create k3d#567