-
Notifications
You must be signed in to change notification settings - Fork 544
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
Start efs stunnel watch dog #104
Comments
I did some quick test by starting the amazon-efs-mount-watchdog from efs mount helper, there are several challenges when using the exiting watch dog. The watch dog is designed for a non-containerized environment where systemd or initd is required to monitor and restart the process if it crashes. And running systemd in a docker container is not trivial. There are two ways I can think of to solve the problem:
|
@leakingtapan I'm seeing this behaviour still on
|
Hello, I have a similar issue, but trying to mount the EFS volume on Fargate
|
@allamand I am getting the same error as you - did you find a solution? |
One of two things fixed this and I'm not sure which because I did both at the same time. The first (and most likely culprit) was Creating a an IAM service account for K8s (scroll down to "Create an IAM policy and role" and look at step 2). the second (and less likely) was by changing the SGs inside of the mount points. Literally the only change I made was the port... I had the SG open to "All Traffic" before and when I narrowed it down to the specific NFS port (2049), it seemed to work. |
I was having the same issue and it was the less likely change of yours that resolved my problem. Although I will say I did the first fix you mentioned initially and then proceeded to do some testing before implementing the secondary fix. Thank you so much for your comment I would have still been pulling out my hair if it wasn't for this comment. |
If you ever start an infrastructure provider please let me know, this answer was more helpful than 8 hours of AWS documentation, Jah Bless |
@lemmikens Thanks!!! this was driving me mad for me it was the SGs on the mount points didnt needs the sa (but im not using the csi driver) |
Is your feature request related to a problem? Please describe.
EFS stunnel watch dog is not started properly due to efs mount helper is installed within container environment. We need to start the watch dog to recover stunnel from crash.
Error message:
That is because there is no proper init system present in the container. This will cause efs stunnel watch dog start to fail here. Although seems an issue, this doesn't seems to be the cause of this issue since the watch dog is never start even in the initial success mount:
Originally posted by @leakingtapan in #103 (comment)
The text was updated successfully, but these errors were encountered: