Fixes issue #2.
Update Instructions for Existing Installations
To fix an existing installation where the file server container is already joined to the AD domain please perform the following steps:
-
Create the directory
/rpool/encrypted/docker/samba/config-fs1/kerberos. -
Create the file
config-fs1/kerberos/krb5.confwith the following content (replacing$DOMAIN_FQDN_UCASEwith your actual domain name in uppercase, e.g.,AD.INTERNAL):
[libdefaults]
default_realm = $DOMAIN_FQDN_UCASE
dns_lookup_realm = false
dns_lookup_kdc = true- Create the
krb5.keytabfile by running the following in your DC container:
samba-tool domain exportkeytab /etc/krb5.keytab- Move
/etc/krb5.keytabfrom the DC container to/rpool/encrypted/docker/samba/config-fs1/kerberoson the host so that it will be mounted to/etc/krb5.keytabin the FS container. - Replace
docker-compose.ymlwith the latest version from this repository which contains the additional bind mounts for the Kerberos files. - Recreate the containers by running:
docker compose down
docker compose up -d- Verify that Kerberos is configured correctly by running the following in your FS container:
kinit administrator
klistIf you don't get errors, everything worked correctly.