User accounts and mounts

[deathblade666]

Hi Looking at the docker compose file you have provided here, insinuates that the /opt/samba-manager/data is where users are stored, but when i check in my container that directory doesn't even exist? so having a time setting up user accounts that persist after restarting the host or downing/upping the container.

/opt/samba-manager# ls
app  requirements.txt  run.py  smb.conf.template  users.json  version.py

[deathblade666]

ok so update ended up creating all these bind mounts and created a backup just in case. now this covers 90%+ of user account persistence however if a user account is created with the "create system user" flag this seems to be missing something as that user account shows in the web ui but does not have access to the share. the real catch is that creating a non system user doesnt work for some reason... so each time i restart my container I need to restore the back up i made to use my user account. Unless someone can point me in the right direction to what else i should create a mount for.

EDIT: after referencing what the backups pull i was able to determine i needed to move to a bind mount, added to the below list (from memory please excuse any misspellings)

      - ./data:/opt/samba-manager #Persists admin account
      - ./smb_config:/etc/samba #Persists shares and samba config
      - ./backups:/var/lib/samba_manager/backups #Persists backups
      - ./smb_data:/var/lib/samba #Persists samba users
      
      # Each file listed below is to persist "system users"
      - ./shadow:/etc/shadow
      - ./gshadow:/etc/gshadow
      - ./passwd:/etc/passwd
      - ./groups:/etc/groups

[lyarinet]

ok so update ended up creating all these bind mounts and created a backup just in case. now this covers 90%+ of user account persistence however if a user account is created with the "create system user" flag this seems to be missing something as that user account shows in the web ui but does not have access to the share. the real catch is that creating a non system user doesnt work for some reason... so each time i restart my container I need to restore the back up i made to use my user account. Unless someone can point me in the right direction to what else i should create a mount for.

EDIT: after referencing what the backups pull i was able to determine i needed to move to a bind mount, added to the below list (from memory please excuse any misspellings)

      - ./data:/opt/samba-manager #Persists admin account
      - ./smb_config:/etc/samba #Persists shares and samba config
      - ./backups:/var/lib/samba_manager/backups #Persists backups
      - ./smb_data:/var/lib/samba #Persists samba users
      
      # Each file listed below is to persist "system users"
      - ./shadow:/etc/shadow
      - ./gshadow:/etc/gshadow
      - ./passwd:/etc/passwd
      - ./groups:/etc/groups

/etc/samba should not be mounted read-only because Samba Manager writes its configuration there. Also, non-system users still need an existing Linux account; Samba-only users are not currently supported by the application. Back up the container and host account files before adding these mounts.

[deathblade666]

ok so update ended up creating all these bind mounts and created a backup just in case. now this covers 90%+ of user account persistence however if a user account is created with the "create system user" flag this seems to be missing something as that user account shows in the web ui but does not have access to the share. the real catch is that creating a non system user doesnt work for some reason... so each time i restart my container I need to restore the back up i made to use my user account. Unless someone can point me in the right direction to what else i should create a mount for.
EDIT: after referencing what the backups pull i was able to determine i needed to move to a bind mount, added to the below list (from memory please excuse any misspellings)

      - ./data:/opt/samba-manager #Persists admin account
      - ./smb_config:/etc/samba #Persists shares and samba config
      - ./backups:/var/lib/samba_manager/backups #Persists backups
      - ./smb_data:/var/lib/samba #Persists samba users
      
      # Each file listed below is to persist "system users"
      - ./shadow:/etc/shadow
      - ./gshadow:/etc/gshadow
      - ./passwd:/etc/passwd
      - ./groups:/etc/groups

/etc/samba should not be mounted read-only because Samba Manager writes its configuration there. Also, non-system users still need an existing Linux account; Samba-only users are not currently supported by the application. Back up the container and host account files before adding these mounts.

as stated in your docker compose file

    volumes:
      - /etc/samba:/etc/samba:ro
      - /var/log/samba:/var/log/samba
      - samba-manager-logs:/var/log/samba-manager
      - samba-manager-users:/opt/samba-manager/data

if this is incorrect it should be updated, the mounts i listed prior are custom ones i set because the ones listed in the compose file (listed above) do not allow for configurations or user's to persist between container restarts.