-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Why delete entrypoint.sh ? #97
Comments
It has changed since switch to s6-overlay in #85 which does not need an entrypoint script as the base s6-alpine image already has one: https://github.com/crazy-max/docker-alpine-s6/blob/aa655e9d8a090907690f244af93be90a8963ce75/Dockerfile#L256
I guess you were mounting a custom But with switch to s6-overlay I don't think you can do this anymore. Maybe I could allow passing additional flags to the process. Have you tried making changes in the yaml config?: global:
- "client min protocol = NT1"
- "server min protocol = NT1"
- "ntlm auth = ntlmv1-permitted" |
Also if what you want with |
I'm running it into a container in a kubernetes cluster, for redundancy, I also tried to modify it from the Dockerfile at the armv8 build stage :
Maybe it should be explicit in the repo if we want to add something else for those who are not familiar with s6 / overlay or add new features like ? btrfs ? ipfs ? Thanks, you can close this ticket. |
If you want to fork and make your own changes feel free to do so but don't think it should be documented here. Also like I said, we could allow additional args being passed to smbd, I would not be against that.
👍 |
Support guidelines
I've found a bug and checked that ...
Description
Hello I liked the entrypoint.sh because I could specify :
Now I don't get the init file point
Expected behaviour
retro compat please ?
Actual behaviour
entrypoint is misplaced
Steps to reproduce
...
Docker info
Docker Compose config
No response
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: