Healthchecks issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- devops, infrastructure
Research direction
Start with the provided Docker Compose configuration and reproduce the unhealthy status while checking how the container's healthcheck handles authenticated SMB access. Read the related crazy-max/docker-samba issue #141 for the smbclient error context. Done means a working authenticated Samba share reports healthy in Portainer without masking genuine failures.
Written by the indexing model from the issue text.
Description
Portainer is showing me the samba container is in an "unhealthy" state. Not sure how to fix that issue.
Although the shares are all working fine without any issues, the healthchecks need to be changed somehow.
Screenshot:
Docker compose file:
services:
samba:
image: dockurr/samba
# image: dperson/samba
container_name: samba
env_file: .samba.env
ports:
- 445:445
volumes:
- /samba/share/:/storage
- /some/folder/conf/smb.conf:/etc/samba/smb.conf
restart: always
samba.env file:
NAME=SHARE_1
USER=user1
PASS=mypassword
UID=1000
GID=1000
smb.conf file:
[global]
server string = SHARE_1 - 192.168.1.100
netbios name = SHARE_1
printing = bsd
printcap name = /dev/null
load printers = no
disable spoolss = yes
server smb encrypt = required
server signing = mandatory
client min protocol = SMB3
client max protocol = SMB3
client smb encrypt = required
client signing = required
hosts allow = 192.168.1.0/24
[SHARE_1]
path = /storage
read only = no
valid users = user1
inherit acls = yes
inherit owner = yes
users.conf file:
#username:UID:groupname:GID:password:homedir
user1:1000:SHARE_1:1000:mypassword
Any idea how to change the healthchecks?
Probably related to:
"The healthcheck fails for me because smbclient also exists with a non zero error when "NT_STATUS_ACCESS_DENIED" is returned (e.g. no anonymous access)."
- Dominant language
- Shell
- Stars
- 840
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from dockur/samba
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
meta::needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
docker-mailserver/docker-mailserver#4864 ·
Maintainers usually reply within 1 day
-
Bump zig to >= 0.17.1 in main images: 0.17.0 emits duplicate LC_LOAD_DYLIB, darwin binaries abort in dyldPossibly taken @SuperQ claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
prometheus/golang-builder#417 ·
Maintainers usually reply within 1 day
-
application-issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Installomator/Installomator#3657 · 1 comment ·
Maintainers usually reply within 3 days
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melodic-software/claude-code-plugins#17374 · 2 comments ·
Maintainers usually reply within 1 day
-
out-of-date
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
CachyOS/CachyOS-PKGBUILDS#2154 ·
Maintainers usually reply within 1 day