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

Blocking anonymous access with "restrict anonymous = 2" causes the healthcheck to fail #101

Open
3 tasks done
wave864 opened this issue Nov 26, 2023 · 0 comments
Open
3 tasks done

Comments

@wave864
Copy link

wave864 commented Nov 26, 2023

Support guidelines

I've found a bug and checked that ...

  • ... the documentation does not mention anything about my problem
  • ... there are no open or closed issues that are related to my problem

Description

global:
  - "restrict anonymous = 2"

in the config file works as intended and blocks anonymous users from seeing the shares on the server, but because the healthcheck seems to be based on an anonymous login with

            "Healthcheck": {
                "Test": [
                    "CMD-SHELL",
                    "smbclient -L \\\\localhost -U % -m SMB3"

it too fails in this config.

Expected behaviour

Restricting anonymous access should not prevent a healthcheck of the container. Maybe having a "healthcheck account" that is baked into the container could solve this problem.

Actual behaviour

see above

Steps to reproduce

see above

Docker info

not required

Docker Compose config

No response

Logs

not required

Additional info

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant