Latest tag fails to init user about samba

[MarvAmBass]

thanks, it seemed to me there are more issues with the container, I've retagged and pushed servercontainers/samba:a3.16.2-s4.15.7-r0 to latest again.

I'll investigate the whole thing - thanks for the hint with the other persons issue!

[gravufo]

Seems like you made a small typo while pushing :D

Nonetheless, I tried the servercontainers/samba:a3.16.2-s4.15.7-r0 tag and it doesn't seem to work either. I'll keep trying older tags and see if one is working and report back.

EDIT: Tried each version of alpine available on DockerHub and they all fail. Either it hasn't worked for quite a while (doesn't make sense, cause your setup would have been broken as well) or there's some weird thing going on on my side...

[MarvAmBass]

ohh thanks, I just pushed t again :)

it works on my machine, even with the broken version from a few days ago.
I get some wierd logs but nothing bad and everything is working

the alpine build log for the samba packages also seemed fine.

I have another open bug ticket, were it seems to have a problem with latest debian - testing I guess. I'm not sure if they broke it, maybe some other new packages breaks my containers I'm not sure. with current stable debian it works just fine.

what kind of host os do you use? I checked the commit you added in your first message, this would create system users, but I explicitly don't want to have system users as a samba user. they are per definition not system users in my optinion

[MarvAmBass]

it tells you, that uid 1000 is in use, which is strange, I don't create a default user, alpine doesn't ship with one.
samba packages also doesn't seem to ship one.

maybe you can use a more random id 1051 and check what user is blocking uid 1000.

[MarvAmBass]

I found some strange thing, as far as I can see in your config, there is a conflict in it:

      ACCOUNT_admin: password
      UID_admin: 1000
      GROUPS_admin: admin
      GROUP_admin: 1000

group admin is autocreated and should not be explicitly added. the group feature is meant for groups you explicitly specify to share files across users.

in your case, adduser or addgroup creates a group/user with 1000 and blocks the other program from using it - this might explain the message, that uid 1000 is already taken. I create the groups first so that they are available on user creation/handling

just remove the GROUP lines in your config and everything should work as expected

      ACCOUNT_admin: password
      UID_admin: 1000

[gravufo]

Thanks a lot for helping, you're totally right, it was indeed the group messing everything up :(

Really appreciate the time and effort!
Have a good one :)