-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: move off-query (ct 115 on off1) docker volume from hdd to nvme #357
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those spontanous reboot as well as the time to copy data are quite alarming :-(
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES | ||
fc762df2e0d9 ghcr.io/openfoodfacts/openfoodfacts-query:sha-7347d944245cc17af4a87b3e704e01c1d0aa7575 "docker-entrypoint.s…" 6 days ago Up 40 minutes 0.0.0.0:5511->5510/tcp, :::5511->5510/tcp off-query-query-1 | ||
a009d86d0656 postgres:12-alpine "docker-entrypoint.s…" 6 days ago Up 50 minutes 5432/tcp off-query-query_postgres-1 | ||
root@off-query:/home/off/off-query-org# docker compose stop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beware launching docker compose commands with root instead of off user.
It's ok to stop, but if you make compose up
with root, you might create permissions problems. So better always do it with user off.
|
||
## Detach old volume on zfs-hdd | ||
|
||
In the Proxmox interface, I detach the old volume, reboot the container, and check that off-query works fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The volume is still to be remove then ?
Note that we have copies of this volume on off2 and ovh3… at some point we might want to remove it !
The new volume should be replicated by itself, because we have a recursive syncoid replication, but better verify it !
Co-authored-by: Alex Garel <alex@garel.org>
No description provided.