Documented switch not supported.
Opened this issue · 4 comments
Hi - the documentation for the installer on the main page suggests --quayStorage is a supported switch, but when specifying it in the latest release (1.2.9), it gives a usage statement error "Error: unknown flag: --quayStorage".
The latest release is 1.3.1, but we didn't have it as a GitHub release. I created releases for new tags. Please check it.
Thank you. I only see the source bundles, not the mirror-registry-[online|offline].tar.gz bundles as in 1.2.9.
I was also surprised by sudden change that moved the storage locations around from 1.3.0 seemingly without any obvious note in release notes in 1.3.0.
As the change requires adding new options to achieve "same results" as before 1.3.0 it would have been nice to mention it somewhere (eg. "due to storage change from 1.3.0 the --quayRoot
no longer control location of data and DB storage, use --pgStorage
and --quayStorage
options for that")
Short summary from what I have seen:
- in 1.2.9 version (and probably before)
# mirror-registry install --quayRoot /mnt/registry
# ls -1 /mnt/registry
pg-data
quay-config
quay-rootCA
quay-storage
- from 1.3.0 if only
--quayRoot
is used, the storage for postgres and quay app will default to volumes in podman which are typically at/var/lib/containers/storage/volumes/
.
# mirror-registry install --quayRoot /mnt/registry
# ls -1 /mnt/registry
quay-config
quay-rootCA
# ls -1 /var/lib/containers/storage/volumes/
...
pg-data
quay-storage
- from 1.3.0 release for results consistent with 1.2.9 behaviour additional options seems to be required
# mirror-registry install --quayRoot /mnt/registry --quayStorage /mnt/registry/quay-storage --pgStorage /mnt/registry/pg-data
# ls -1 /mnt/registry
pg-data
quay-config
quay-rootCA
quay-storage
If above can be in some form included in README that may help the future deployments. Also to stay within what this issue is about - adding 'since 1.3.0' to --quayStorage
and --pgStorage
documentation might do the trick too.