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

The smb protocol is not available #619

Open
XDDK opened this issue Aug 10, 2024 · 1 comment
Open

The smb protocol is not available #619

XDDK opened this issue Aug 10, 2024 · 1 comment
Labels
needs info Not enough information provided question Further information is requested

Comments

@XDDK
Copy link

XDDK commented Aug 10, 2024

The issue is simple and opened in multiple places because the nextcloud image doesn't install the required dependencies for the smbshare in the Dockerfile.

"smbclient" is not installed. Mounting of "SMB/CIFS", "SMB/CIFS using OC login" is not possible. Please ask your system administrator to install it.
image

I've tried multiple solutions to fix this myself besides changing the Dockerfile because I have to run an image that will not always be up with the helm configuration standards.

Solutions tried:

  1. run an init container that installs smbclient and puts it on a mounted folder which is read in the PATH variable (worked partially)
  2. run a before-starting hook to install the smbclient and/or the php-smbclient (didn't work)
  • The first solution worked partially, meaning nextcloud saw the binary and recognised the smb protocol allowing me to add a smb external share but I do get this error when adding it (with same info as in my local machine, nb I also checked the ping to the server and is good from the container)
    image

  • The second solution didn't work at all because of multiple issues with the permissions and I don't want to give root permissions to the entire pod and to all of my containers.

Can anyone help me in order to solve this until nextcloud fixes this feature in the helm charts?
Nextcloud contributors, please consider adding this to the default installation.

Thank you everyone!

@joshtrichards
Copy link
Member

joshtrichards commented Sep 8, 2024

See #205 (comment) for an example.

I've tried multiple solutions to fix this myself besides changing the Dockerfile because I have to run an image that will not always be up with the helm configuration standards.

Extending the Dockerfile is the correct way. I'm not clear what you mean by "have to run an image that will not always be up with the helm configuration standards" so I'm not able to respond to that part of your statement. Can you clarify what you mean?

@joshtrichards joshtrichards added needs info Not enough information provided question Further information is requested labels Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info Not enough information provided question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants