You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Seafile Rock-On install fails with: manifest for seafileltd/seafile-mc:latest not found when trying to pull the image. This is because upstream has moved to using versioned latest tags: 10.0-latest, 11.0-latest, 12.0-latest.
Current version seems to be 12.0, and its docker install is detailed/documented at: https://manual.seafile.com/12.0/setup/setup_ce_by_docker/
The first is just a collection of ENV that we can pick and choose from; no issue there, it seems.
The second is the docker-compose file with all settings and volumes required. Note the use of multi-containers "linked" together with a docker network. This could be problematic for us at this point.
The third is the docker-compose file for the reverse proxy they now use: caddy. Note the use of ports 80 and 443 and the docker network of file 2.
The text was updated successfully, but these errors were encountered:
Thanks to forum user @silviucc for reporting this issue:
https://forum.rockstor.com/t/cant-install-seafile-rockon/10353
The current Seafile Rock-On install fails with:
manifest for seafileltd/seafile-mc:latest not found
when trying to pull the image. This is because upstream has moved to using versionedlatest
tags: 10.0-latest, 11.0-latest, 12.0-latest.Current version seems to be 12.0, and its docker install is detailed/documented at: https://manual.seafile.com/12.0/setup/setup_ce_by_docker/
Its settings are split into 3 files:
https://manual.seafile.com/12.0/docker/ce/env
https://manual.seafile.com/12.0/docker/ce/seafile-server.yml
https://manual.seafile.com/12.0/docker/caddy.yml
The first is just a collection of ENV that we can pick and choose from; no issue there, it seems.
The second is the docker-compose file with all settings and volumes required. Note the use of multi-containers "linked" together with a docker network. This could be problematic for us at this point.
The third is the docker-compose file for the reverse proxy they now use: caddy. Note the use of ports 80 and 443 and the docker network of file 2.
The text was updated successfully, but these errors were encountered: