search

JensErat / docker-seafile

Dockerfile for a Seafile 5 image. Not maintained any more.
https://hub.docker.com/r/jenserat/seafile/
ISC License
80 stars 41 forks source link

symlink probably not added #9

Closed mancvso closed 9 years ago

mancvso commented 9 years ago

Hi! The startup scripts (those that run when autostart=true) are referencing /opt/seafile/seafile-server-latest but the symbolic link is never created, thus the services are never executed on boot. I've had to do that manually with ln -s /opt/seafile/seafile-server-4.0.5 /opt/seafile/seafile-server-latest Am I missing something?

JensErat commented 9 years ago

Seafile is not ready yet for "automatic upgrades", thus all the setup stuff has to be done manually yet. Did you run the setup? This should add the link without manual internvention.

I already had some thoughts on automating the database upgrades, and will integrate the current seafile version in the image (so no downloader any more, maybe even split up the image in multiple ones to be really "Docker-compliant"). Will takes some more weeks as Seafile isn't an easy service to cleanly put into Docker's paradigms, but this will happen. Definitely.

mancvso commented 9 years ago

Ahm... I've switched versions without a single issue (3.0.4 -> 3.1.6 -> 4.0.5). But you are right; a layered history (tags) is more "Dockerish" approach.

JensErat commented 9 years ago

So the issue is resolved for now? I closed the issue, if you've still got problems just reply again.

mancvso commented 9 years ago

Still needed to use the symlink when upgrading.

JensErat commented 9 years ago

I will look into cleaning up the Dockerfile soon, need to upgrade my own setup anyway. I guess until then symlinking manually should be fine.