search

VGoshev / seafile-docker

Docker image for Seafile server
https://hub.docker.com/r/sunx/seafile/
MIT License
27 stars 19 forks source link

Latest build broken #12

Closed rhaamo closed 5 years ago

rhaamo commented 5 years ago

Issue seems here: https://github.com/VGoshev/seafile-docker/blob/946714d85beb7a1137b5e51424b839455c7d66f8/docker/docker-run-root#L10

I think it's needed to add a space after [

Log:

groupmod: PAM: Permission denied
usermod: no changes
uid=2016(seafile) gid=2016(seafile) groups=2016(seafile),2016(seafile)
/bin/docker-run-root: line 18: [seafile: not found
su-exec: setgroups: Operation not permitted
VGoshev commented 5 years ago

Ou, really, thanks. Although other errors: groupmod: PAM: Permission denied and su-exec: setgroups: Operation not permitted aren't related to this space issue. Do you have SELinux activated on your host?

rhaamo commented 5 years ago

no I don't have selinux at all. does this use something specific to some docker version ?

VGoshev commented 5 years ago

Nope, nothing specific to docker, just switching from root to seafile user. I'll think, what could cause this issue and how to fix it

rhaamo commented 5 years ago

I've only found https://github.com/ncopa/su-exec/issues/2 which talk about filesystem permissions.

rhaamo commented 5 years ago

That su-exec doesn't seems to apply since there is no USER here.

I've recreated from scratch the container (instead of duplicate/edit in portainer) and it seems to work.

I guess it was needing something caps related which wasn't present in the "old" definition of the container I had.

Anyway, my seafile is back alive, thanks !