The smb protocol is not available
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
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.
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:
- run an init container that installs smbclient and puts it on a mounted folder which is read in the PATH variable (worked partially)
- 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)
-
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Dockerfile and Helm configuration referenced in the report, then reproduce an SMB/CIFS external-share mount using the chart's default image. Trace how the image supplies smbclient and how the pod runs it; done means the default deployment can add and use SMB shares without manual init-container or hook changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100