-
Notifications
You must be signed in to change notification settings - Fork 57
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
Kurtosis can't run linuxserver/wireguard #2405
Comments
@jshufro Sir, you can leave your email address. I want to ask you questions |
hey @jshufro Gyani from Kurtosis here. Thank you for writing this ticket. We don't support disabling tini out of the box and will have to add support for it. Can you tell me more about your usecase? In the meantime I will try to compile a version of Kurtosis with tini disabled and run your script |
Looking at your main.star further Can you try removing ENTRYPOINT CMD set to [] and see if it runs? It has to have something for it to run. Not setting them is using the default values
this works just fine. You will have to add back wg_conf; |
EDIT: never mind, I still see:
|
Interesting, I am pretty sure I could get it to run on Friday but now I can confirm that I am seeing what you are seeing. More over this change - #2412 seems to get it to work but we would like to put it behind a Starlark interface so that users can switch it on/off willingly. Can you tell me more about your usecase? |
Closes #2405 --------- Co-authored-by: leoporoli <[email protected]>
What's your CLI version?
0.88.18
Description & steps to reproduce
Putting:
in main.star leads kurtosis to fail to start a perfectly good docker container with the following error:
s6-overlay-suexec: fatal: can only run as pid 1
I believe this is because of b8989a8
Is there a way to turn off the use of docker
--init
?Desired behavior
Wireguard should start
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
Other: anything not covered by the above
The text was updated successfully, but these errors were encountered: