You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
I want to use your samba container on a fedora server. Fedora server uses podman for container managemend instead of docker. When I try to use my docker-compose.yaml I got the following issue:
INTERNAL ERROR: open_sockets_smbd() failed insmbd () () pid 857 (4.19.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 857): open_sockets_smbd() failed in 4.19.9
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smbd version 4.19.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd_open_one_socket: open_socket_in failed: Permission denied
smbd_open_one_socket: open_socket_in failed: Permission denied
open_sockets_smbd: No sockets available to bind to.
===============================================================
When I try the same config with Docker, everything works as expected. Even in privileged mode or the capability SYS_ADMIN the error occures.
Expected behaviour
The container comes up and I can discover/read/write the smb shares.
Actual behaviour
The Container "crashes" with the following error:
INTERNAL ERROR: open_sockets_smbd() failed insmbd () () pid 857 (4.19.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 857): open_sockets_smbd() failed in 4.19.9
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smbd version 4.19.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd_open_one_socket: open_socket_in failed: Permission denied
smbd_open_one_socket: open_socket_in failed: Permission denied
open_sockets_smbd: No sockets available to bind to.
===============================================================
Steps to reproduce
Create the required directory
run the following command podman run -d --network host \ --security-opt label=disable -e LOG_LEVEL=debug -v "./data:/data" -v "./misc:/samba/misc" -v "./backup:/samba/backup" \ --privileged --name samba crazymax/samba
>>>> Executing external compose provider "/usr/libexec/docker/cli-plugins/docker-compose". Please see podman-compose(1) for how to disable this message. <<<<name: sambaservices:
samba:
container_name: sambaenvironment:
SAMBA_LOG_LEVEL: "0"TZ: Europe/Berlinimage: crazymax/sambanetwork_mode: hostrestart: alwayssecurity_opt:
- label=disablevolumes:
- type: bindsource: /home/tom/Documents/github/tzabbi/homelab/samba-test/datatarget: /databind:
create_host_path: true
- type: bindsource: /home/tom/Documents/github/tzabbi/homelab/samba-test/misctarget: /samba/miscbind:
create_host_path: true
- type: bindsource: /home/tom/Documents/github/tzabbi/homelab/samba-test/backuptarget: /samba/backupbind:
create_host_path: true
Logs
$ podman logs samba
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-config.sh: executing...
Setting timezone to UTC
Initializing files and folders
Setting global configuration
Creating user l-backup/l-backup (1000:1000)
Creating user tom/tom (1001:1001)
Creating share misc
Creating share backup
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)
# Global parameters
[global]
WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients results in undefined behaviour.
Server role: ROLE_STANDALONE
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
smb1 unix extensions = No
smb ports = 445
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
[misc]
comment = everything can be stored here
guest ok = Yes
path = /samba/misc
valid users = tom
vfs objects = recycle
write list = tom
recycle:versions = yes
recycle:keeptree = yes
recycle:repository = .recycle
[backup]
guest ok = Yes
path = /samba/backup
read only = No
valid users = backup
write list = backup
[cont-init.d] 01-config.sh: exited 0.
[cont-init.d] 02-svc-smbd.sh: executing...
[cont-init.d] 02-svc-smbd.sh: exited 0.
[cont-init.d] 03-svc-wsdd2.sh: executing...
[cont-init.d] 03-svc-wsdd2.sh: exited 0.
[cont-init.d] ~-socklog: executing...
[cont-init.d] ~-socklog: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
smbd version 4.19.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd_open_one_socket: open_socket_in failed: Permission denied
smbd_open_one_socket: open_socket_in failed: Permission denied
open_sockets_smbd: No sockets available to bind to.
===============================================================
INTERNAL ERROR: open_sockets_smbd() failed in smbd () () pid 803 (4.19.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 803): open_sockets_smbd() failed in 4.19.9
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smbd version 4.19.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd_open_one_socket: open_socket_in failed: Permission denied
smbd_open_one_socket: open_socket_in failed: Permission denied
open_sockets_smbd: No sockets available to bind to.
===============================================================
INTERNAL ERROR: open_sockets_smbd() failed in smbd () () pid 851 (4.19.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 851): open_sockets_smbd() failed in 4.19.9
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smbd version 4.19.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd_open_one_socket: open_socket_in failed: Permission denied
smbd_open_one_socket: open_socket_in failed: Permission denied
open_sockets_smbd: No sockets available to bind to.
===============================================================
INTERNAL ERROR: open_sockets_smbd() failed in smbd () () pid 857 (4.19.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 857): open_sockets_smbd() failed in 4.19.9
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smbd version 4.19.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd_open_one_socket: open_socket_in failed: Permission denied
smbd_open_one_socket: open_socket_in failed: Permission denied
open_sockets_smbd: No sockets available to bind to.
===============================================================
INTERNAL ERROR: open_sockets_smbd() failed in smbd () () pid 863 (4.19.9)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 863): open_sockets_smbd() failed in 4.19.9
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
Additional info
I'm using Fedora 41.
Podman version:
Client: Podman Engine
Version: 5.3.1
API Version: 5.3.1
Go Version: go1.23.3
Built: Thu Nov 21 01:00:00 2024
OS/Arch: linux/amd64
The text was updated successfully, but these errors were encountered:
Support guidelines
I've found a bug and checked that ...
Description
I want to use your samba container on a fedora server. Fedora server uses podman for container managemend instead of docker. When I try to use my
docker-compose.yaml
I got the following issue:When I try the same config with Docker, everything works as expected. Even in privileged mode or the capability SYS_ADMIN the error occures.
Expected behaviour
The container comes up and I can discover/read/write the smb shares.
Actual behaviour
The Container "crashes" with the following error:
Steps to reproduce
podman run -d --network host \ --security-opt label=disable -e LOG_LEVEL=debug -v "./data:/data" -v "./misc:/samba/misc" -v "./backup:/samba/backup" \ --privileged --name samba crazymax/samba
Docker info
Docker Compose config
Logs
Additional info
I'm using Fedora 41.
Podman version:
Client: Podman Engine
Version: 5.3.1
API Version: 5.3.1
Go Version: go1.23.3
Built: Thu Nov 21 01:00:00 2024
OS/Arch: linux/amd64
The text was updated successfully, but these errors were encountered: