-
Notifications
You must be signed in to change notification settings - Fork 5
Creation of initial seafile admin fails #5
Comments
Could you give some information on the Docker and Docker-compose versions used? I have a similar setup in use with an NGINX Reverse proxy and that definitely doesn't interfer. This indeed is a strange bug because the Travis Build runs some unit tests and the admin creation is essential for anything to work.
|
My Docker host is an Ubuntu server 17.10 machine, with Docker version I've been testing around some more (also based on your questions). Not mounting the volume still gives the same creation error, so it does not seem to be a permission error on the volume itself. As far as any However, I found something interesting. Executing the
So this seems to be an issue related to Docker-compose? |
This is super weird. To my understanding Could you post the logs of Docker after trying to create the container using |
The following is the resulting log of specifically creating the container. Using
And using
They seem identical regarding the operations themselves. The moment the creation error pops up, there is no log entry created by Docker. Could it be a rights issue, that |
Just encountered similar with a manual build on Ubuntu 20.04 and Seafile 7.1.5 Starting seahub.sh asks for admin email and password then gives the above error "Error happened during creating seafile admin" Except in my case I cannot access the site at this point and on server curl 127.0.0.1:8000 returns nothing Of note I did need to install libmemcached-dev via apt before I could install pylibmc and django-pylibmc via pip3 |
When spinning up a fresh container, I receive the following error halfway through the initial setup script:
This is a snippet from the logs. The container starts fine, and I can actually get to the login page, but since the admin account has not been created, I cannot log in.
I've been digging through the Seafile codebase to find out where this pops up, and it looks like the
check_init_admin.py
file is where the exception is thrown, which is called byseahub.sh
.I'm creating the container using the following
docker-compose
:There is another reverse proxy in front of this container. I'm assuming this won't interfere with the admin creation process, but I'm still mentioning it just in case.
By the way: thanks for creating this. It is much, much better than the strange dockerfile wrapper script presented by the Seafile devs themselves.
The text was updated successfully, but these errors were encountered: