Does anybody have a working guide/video-tutoria to follow to configure Seafile correctly on OMV via docker?
Many thanks
Does anybody have a working guide/video-tutoria to follow to configure Seafile correctly on OMV via docker?
Many thanks
Have you read this doc ? What do you want to know ?
You will find my working configuration in attachments. Just replace Host IP and Host Path.
Thanks for this. I have created the two variables:
SEAFILE_ADMIN_EMAIL and SEAFILE_ADMIN_PASSWORD, but I don't seem to be able to login.
Nothing in the log it can help as far as I can tell...
I've also tryed the manual credential reset procedure:
root@NAS:/opt/seafile-server-latest# ./reset-admin.sh -h
Traceback (most recent call last):
File "/opt/seafile-server-6.3.4/seahub/manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/opt/seafile-server-6.3.4/seahub/thirdpart/django/core/management/__init__.py", line 364, in execute_from_command_line
utility.execute()
File "/opt/seafile-server-6.3.4/seahub/thirdpart/django/core/management/__init__.py", line 356, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/seafile-server-6.3.4/seahub/thirdpart/django/core/management/base.py", line 283, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/seafile-server-6.3.4/seahub/thirdpart/django/core/management/base.py", line 330, in execute
output = self.handle(*args, **options)
File "/opt/seafile-server-6.3.4/seahub/seahub/base/management/commands/createsuperuser.py", line 88, in handle
User.objects.get(email=default_username)
File "/opt/seafile-server-6.3.4/seahub/seahub/base/accounts.py", line 94, in get
emailuser = ccnet_threaded_rpc.get_emailuser(email)
File "/opt/seafile-server-6.3.4/seafile/lib64/python2.7/site-packages/pysearpc/client.py", line 110, in newfunc
ret_str = self.call_remote_func_sync(fcall_str)
File "/opt/seafile-server-6.3.4/seafile/lib64/python2.7/site-packages/ccnet/rpc.py", line 71, in call_remote_func_sync
client = self.pool.get_client()
File "/opt/seafile-server-6.3.4/seafile/lib64/python2.7/site-packages/ccnet/pool.py", line 29, in get_client
client = self._create_client()
File "/opt/seafile-server-6.3.4/seafile/lib64/python2.7/site-packages/ccnet/pool.py", line 21, in _create_client
client.connect_daemon()
File "/opt/seafile-server-6.3.4/seafile/lib64/python2.7/site-packages/ccnet/client.py", line 131, in connect_daemon
return self.connect_daemon_with_pipe()
File "/opt/seafile-server-6.3.4/seafile/lib64/python2.7/site-packages/ccnet/client.py", line 113, in connect_daemon_with_pipe
raise NetworkError("Can't connect to daemon")
ccnet.errors.NetworkError: Can't connect to daemon
Alles anzeigen
Have you read this doc ? What do you want to know ?
You will find my working configuration in attachments. Just replace Host IP and Host Path.
Thanks, these photos helped me out, I had missed the SEAFILE_SERVER_HOSTNAME and I wasn't able to download anything.
And also the "/shared" option now gives me the option to save the files elsewhere and to be able to rebuild the container.
Thanks for the info
Have you read this doc ? What do you want to know ?
You will find my working configuration in attachments. Just replace Host IP and Host Path.
Hi RPMan, and thanks for the info. A short info though: as you have now your configuration with the bridged local IP and the port 7000, does that mean that you are accessing the seafile server on the same ip as the omv host ip but on port 7000?
me, I run OMV on the bare metal and when I tried to follow the procedure of seafile installation I was getting the following error:
ERROR: for seafile Cannot start service seafile: driver failed programming external connectivity on endpoint seafile (117fac6d5b104a11ac4beefb34558e17a2742fe1f8aabb06d2ec96746c1ac66a): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
ERROR: Encountered errors while bringing up the project.
which, by my understanding is that, the docker was trying to make himself available on the same IP as the OMV host on port 80, conflicting thus with the OMV's nginx...
What I have done is to update in the docker-compose.yml the ports definition to
Now my OMV host 8080 port points to my docker 80 port and I can access it through my OMV host IP like this: 192.168.1.10:80
I am posting this one, as it took me a while until to manage it... this is one way to do it but I think I will move to a solution where the docker will take his own local IP and I can access it directly on port 80.... seems a bit more clean and lean...
Hi RPMan, and thanks for the info. A short info though: as you have now your configuration with the bridged local IP and the port 7000, does that mean that you are accessing the seafile server on the same ip as the omv host ip but on port 7000?
Yes.
which, by my understanding is that, the docker was trying to make himself available on the same IP as the OMV host on port 80, conflicting thus with the OMV's nginx...
Yes.
this is one way to do it but I think I will move to a solution where the docker will take his own local IP and I can access it directly on port 80.... seems a bit more clean and lean...
It's totally fine to access seafile with omv ip and with port forwarding (8080:80). It's not worse than a dedicated IP ...
Doesn't Seafile have a docker? Seems to be a perfect app for it.
Hey Guys, I am stuck at the start. I installed Docker and activated Docker GUI in the Dashboard, but know I dont know how to grab the docker image and install the container. Could you provide me the neccessary steps. It would be highly appreaciated. Cheers, David
This guide is a good introduction in Docker using the Docker-gui
OMV + Docker plugin media server (Plex, PlexPy, Ombi, Libresonic, NZBGet, ruTorrent, Sonarr, Radarr, Mylar, and more)
If you have a look at the first 2-3 examples you might be able to setup seafile on your own.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!