Closed hnrd closed 1 year ago
Oh i'm sorry. I closed it as a duplicate but it's not exactly, just caused by the same underlying issue. Feel free to reopen if you like :)
It's fine to close. I just wanted to document findings a bit more, as it's not really related to k8s :)
Describe the bug with a clear and concise description of what the bug is.
Placing the storage directory on a NFS mount results in
error creating storage backend: bad file descriptor
What's your GoToSocial Version?
0.5.2, 0.5.1-SNAPSHOT@ad08c6c22987d31d9ead0429aae5fb84555b3cc2
GoToSocial Arch
amd64 docker
Browser version
No response
What happened?
To research #950 I built a test setup without k8s, just starting GoToSocial locally and using a NFS share for it's storage. This results in the same error, the storage backend errors out:
What you expected to happen?
The service to initialize the storage system.
How to reproduce it?
see docker command above. I also ran the gotosocial binary without docker to the same (erroneous) result.
Anything else we need to know?
These are the NFS mount options:
This is how the storage directory looks after the crash: