Skip to content
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

when docker stopped the mounted decrypt points became 'Transport endpoint is not connected' #2

Open
skygunner opened this issue Jan 13, 2021 · 1 comment

Comments

@skygunner
Copy link

Hi ,

Thanks for the nice handy docker image.
I tried to use this docker image on unraid nas, it works fine for mounting.
But when the container stopped, the none-empty folders of CIPHERDIR will became 'Transport endpoint is not connected' and need to umount -l to them. Otherwise the next start of the container will error out due to

can't create directory '/mnt/a-folder': Socket not connected

Is this a file permission issue or a recent change in the gocryptfs?

I remember I use the older gocryptfs and have no such issue.

@OJFord
Copy link
Owner

OJFord commented Jan 15, 2021

Did you run fusermount -u? The readme notes that it isn't run automatically - to be honest though I can't remember why not.

If that is the issue, it's probably worth sorting out - it's a bit of an odd gotcha.

trapping Docker's STOPSIGNAL in the run script and unmounting on exit ought to do it. A PR would be great, or I might have a look at the weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants