instantlinux/samba repository overview

⁠samba

Samba as a file server. This is stripped down to the basics to enable greatest flexibility. Supported on multiple architectures.

⁠Usage

The most-common directives can be specified in environment variables as shown below. If you need further customizations, put them in one or more files under mount point /etc/samba/conf.d. If you want to add global settings, put those into the first file with a name like 0globals.conf -- they will be appended in alphabetical-sort sequence.

Samba requires mapping between Unix user IDs and Windows identities. The simplest way to do that is create a file users.sh mounted under /etc/samba/conf.d with group and username entries in this form:

addgroup -g 1234 groupname
adduser -D -H -G groupname -u 5678 myself

and set passwords in a file /var/lib/samba/private/passwd.tdb using the smbpasswd utility after starting the container:

docker exec -it samba_app_1 smbpasswd -a myself
New SMB password:
Retype new SMB password:
Added user myself.

See Samba IDMAP⁠ documentation for the many other supported identity mapping options. This repo has complete instructions for building a kubernetes cluster⁠ where you can launch with helm⁠ or kubernetes.yaml⁠ using make and customizing Makefile.vars⁠ after cloning this repo:

git clone https://github.com/instantlinux/docker-tools.git
cd docker-tools/k8s
make samba

⁠Variables

These variables can be passed to the image from helm values.yaml, kubernetes.yaml or docker-compose.yml as needed:

⁠Notes

• Older versions of samba published here can be used as a workaround for clients that need smb v1 / NT1 protocol. For example, Sonos S1 devices won't work with samba 4.15.x; you can run this container with tag 4.13.7-r0 and set server min protocol = NT1 global directive to support such use cases.

⁠Contributing

If you want to make improvements to this image, see CONTRIBUTING⁠.