-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Bug]: k3s > 1.24.x will not start #6770
Comments
It seems to be a matter of starting a container with another flag as per this docs page: |
Overriding |
In my case, it worked with DockerImageName
.parse("rancher/k3s:v1.25.10-k3s1"))
.withLogConsumer(Slf4jLogConsumer(logger))
.withCommand(
"server",
"--disable=traefik",
"--tls-san=${DockerClientFactory.instance().dockerHostIpAddress()}") |
The flag https://docs.k3s.io/cli/server#deprecated-options That means this module is broken out of the box for more than a year. Switching to the |
Replace `--no-deploy` and use `--disable` instead. Fixes #6770 --------- Co-authored-by: Eddú Meléndez <eddu.melendez@gmail.com>
Module
K3S
Testcontainers version
1.17.6
Using the latest Testcontainers version?
Yes
Host OS
Ubuntu 20.04 on WSL2 on Windows 11
Host Arch
x86
Docker version
What happened?
k3s testcontainer will not start. Log message:
for k3s 1.25.x
for k3s 1.26.x
I traced it back to this line
testcontainers-java/modules/k3s/src/main/java/org/testcontainers/k3s/K3sContainer.java
Line 44 in c90daab
see also https://docs.k3s.io/reference/server-config#deprecated-options
Workaround is to use k3s<=1.24.x
Relevant log output
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: