Open antmerlino opened 2 years ago
Do you have the same issue with this cap?:
$ docker run --cap-add=sys_nice -p 445:445 -v "$(pwd)/data:/data" -e SAMBA_LOG_LEVEL=3 --name samba-test crazymax/samba
@crazy-max Yes same issue. No differences.
I'm not able to repro on an M1 mac mini (macOS Monterey 12.3.1) with Docker Desktop 4.10.1:
$ docker run --rm -it crazymax/samba
Setting timezone to UTC
Initializing files and folders
Setting global configuration
parse error: Invalid numeric literal at line 1, column 6
parse error: Invalid numeric literal at line 1, column 6
parse error: Invalid numeric literal at line 1, column 6
parse error: Invalid numeric literal at line 1, column 6
parse error: Invalid numeric literal at line 1, column 6
parse error: Invalid numeric literal at line 1, column 6
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE
# Global parameters
[global]
disable netbios = Yes
disable spoolss = Yes
dns proxy = No
local master = No
map to guest = Bad User
pam password change = Yes
printcap name = /dev/null
security = USER
server role = standalone server
server services = s3fs, rpc, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate
server string = Docker Samba Server
smb ports = 445
unix extensions = No
usershare allow guests = Yes
winbind scan trusted domains = Yes
fruit:time machine = yes
fruit:delete_empty_adfiles = yes
fruit:wipe_intentionally_left_blank_rfork = yes
fruit:veto_appledouble = no
fruit:posix_rename = yes
fruit:model = MacSamba
fruit:metadata = stream
idmap config * : backend = tdb
create mask = 0664
directory mask = 0775
force create mode = 0664
force directory mode = 0775
hosts allow = 127.0.0.0/8 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16
hosts deny = 0.0.0.0/0
printing = bsd
strict locking = No
vfs objects = fruit streams_xattr
wide links = Yes
smbd version 4.15.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2021
Not sure what the issue is
The only thing I notice is that you are running Monterey 12.3.1 and I'm running 12.5. Perhaps they updated something security-wise that's having an effect?
I'm having the same issue on my MacBook Pro (Intel) running macOS Ventura 13.1 (22C65).
I'm ready to help debugging this issue if needed.
I'm able to start the container without any apparent issues with the following command:
$ docker run -p 445:445 -v "$(pwd)/data/config.yml:/data/config.yml" -e SAMBA_LOG_LEVEL=3 --name samba-test crazymax/samba
The only difference is the direct mapping of the configuration file instead of the entire data
directory. Could it be permissions related?
Edit
A working example is available here: https://gitlab.com/coloc-malakof/coloc-malakof/-/tree/main/samba
I've been able to keep the cache
directory as a Docker volume as the lib
directory inside /data
seems to cause the issue.
A working example is available here: https://gitlab.com/coloc-malakof/coloc-malakof/-/tree/main/samba
Thanks for that, super helpful!
Behaviour
I am trying to run this container on Mac and the container immediately exits. Enabling a higher log level, I get the following:
Steps to reproduce this issue
config.yml
Expected behaviour
Container should run and be able to bind.
Actual behaviour
Container immediately exits
Configuration
Docker info
Logs