Iām getting this message from your registry, SSL error using Docker v1.11.2
Error response from daemon: Get https://registry.git.dmfy.gov.cn/v1/_ping: x509: certificate is valid for git.wangyan.org, not registry.git.dmfy.gov.cn
Workaround is to do git clone https://github.com/wangyan/docker-seafile and then docker build . and finally docker tag <docker-id> wangyan/docker-seafile:latest
end result:
REPOSITORY TAG IMAGE ID CREATED SIZE wangyan/docker-seafile latest b7e0542f85d0 2 minutes ago 403.6 MB wangyan/docker-seafile v2.1.0 b7e0542f85d0 2 minutes ago 403.6 MB
How do you plan to upgrade to the next seafile version? According to the seafile upgrade guide you should execute one or several shell scripts to successfully switch to the next version. Also those shell scripts may contain the new mysql table schemas especially on a major upgrades. But how it will be possible when you are running seafile in a separate container?
Just read this by chance. Though I donāt use docker at the moment as far as I understood it is not the idea to upgrade something in a docker container. If something doesnāt work or the software is outdated you donāt fix/upgrade a container but you throw it away and start a new/upgraded container provided by the maintainer (or build your own). This idea is called āpets versus cattleā.
Did you look at the seafile upgrade guide?
Weāre talking not about how to switch between different seafile versions within docker container but rather how can you execute shell script which is provided with a new seafile release to make a successfull migration to the next major or minor release.
if this is pointing to me: yes I know the upgrade guide. For a minor upgrade you (basically) stop the seafile processes, switch to seafile system user, download the new version, extract it, switch to the new-version-folder /upgrade and for example start a tiny version upgrade with ./minor-upgrade.sh - then the upgrade process should start (for a tiny version upgrade in this case, like 6.0.3 to 6.0.4).
Anway: in my opinion this is not something you do when working with docker containers (in my opinion). For docker you should just kick out your current seafile container and pull the one with the new version. No upgrade script - this is something the container maintainer (@wangyan?) does for you (but maybe I still missunderstand you - sry in this case).