installation nfs share problem #147
-
|
Hi, when i try to install 0.7.1 using a nfs export as sharedDir (config.toml) Folder xxx (and all parents of the shared folder) must have group and other execute permissions the service account has rwx on that share. thanks for helping Florian |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hi Florian, It's a little hard to tell what's going on here from your description, but is there any chance your issue is the same as another related issue that was reported recently? https://github.com/orgs/nextpyp/discussions/142 This particular permission check in the installer is trying to check for a permission mis-configuration issue early on, before other processes after the installation can fail, but we've learned the check logic isn't universally correct in all environments. So, there are some environments where the check will incorrectly fail. We're working on improving the installation logic in the next update, but in the meantime, you can edit the installation script to skip the check entirely, and then hope none of the processes after installation actually fail. The linked issue has more detailed information if you want to go that route. |
Beta Was this translation helpful? Give feedback.
-
|
commented the check in the script
... worked.
thanks
Florian
…________________________________
Von: Jeff Martin ***@***.***>
Gesendet: Donnerstag, 7. August 2025 17:13:36
An: nextpyp/.github
Cc: Beck, Florian; Author
Betreff: Re: [nextpyp/.github] installation nfs share problem (Discussion #147)
Hi Florian,
It's a little hard to tell what's going on here from your description, but is there any chance your issue is the same as another related issue that was reported recently?
#142
This particular permission check in the installer is trying to check for a permission mis-configuration issue early on, before other processes after the installation can fail, but we've learned the check logic isn't universally correct in all environments. So, there are some environments where the check will incorrectly fail. We're working on improving the installation logic in the next update, but in the meantime, you can edit the installation script to skip the check entirely, and then hope none of the processes after installation actually fail. The linked issue has more detailed information if you want to go that route.
—
Reply to this email directly, view it on GitHub<#147 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAUYRLVZ6YT6GJBQCH4TBD3MNUKBAVCNFSM6AAAAACDIBHT2GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBTGYYTOMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hi Florian,
It's a little hard to tell what's going on here from your description, but is there any chance your issue is the same as another related issue that was reported recently?
https://github.com/orgs/nextpyp/discussions/142
This particular permission check in the installer is trying to check for a permission mis-configuration issue early on, before other processes after the installation can fail, but we've learned the check logic isn't universally correct in all environments. So, there are some environments where the check will incorrectly fail. We're working on improving the installation logic in the next update, but in the meantime, you can edit the installation script to skip th…