docker: use containerd-snapshotter #739

Merged
mg merged 6 commits from containerd-snapshotter into master 2025-11-28 20:43:32 +01:00
Owner
https://docs.docker.com/engine/storage/containerd/ closes #734
mg added 2 commits 2025-11-28 20:28:31 +01:00
dd
All checks were successful
/ shellcheck (pull_request) Successful in 3s
/ gitleaks (pull_request) Successful in 3s
/ ansible-lint (pull_request) Successful in 41s
7ac68cb0cb
mg added 2 commits 2025-11-28 20:36:25 +01:00
fg
All checks were successful
/ shellcheck (pull_request) Successful in 2s
/ gitleaks (pull_request) Successful in 2s
/ ansible-lint (pull_request) Successful in 36s
7f97857da8
dd
Some checks failed
/ shellcheck (pull_request) Successful in 2s
/ gitleaks (pull_request) Successful in 2s
/ ansible-lint (pull_request) Failing after 14m23s
de7c071f77
gg
All checks were successful
/ shellcheck (pull_request) Successful in 3s
/ gitleaks (pull_request) Successful in 3s
/ ansible-lint (pull_request) Successful in 47s
2990050a81
Author
Owner
lldap-db  | Error: in 18+, these Docker images are configured to store database data in a
lldap-db  |        format which is compatible with "pg_ctlcluster" (specifically, using
lldap-db  |        major-version-specific directory names).  This better reflects how
lldap-db  |        PostgreSQL itself works, and how upgrades are to be performed.
lldap-db  |
lldap-db  |        See also https://github.com/docker-library/postgres/pull/1259
lldap-db  |
lldap-db  |        Counter to that, there appears to be PostgreSQL data in:
lldap-db  |          /var/lib/postgresql/data (unused mount/volume)
lldap-db  |
lldap-db  |        This is usually the result of upgrading the Docker image without
lldap-db  |        upgrading the underlying database using "pg_upgrade" (which requires both
lldap-db  |        versions).
lldap-db  |
lldap-db  |        The suggested container configuration for 18+ is to place a single mount
lldap-db  |        at /var/lib/postgresql which will then place PostgreSQL data in a
lldap-db  |        subdirectory, allowing usage of "pg_upgrade --link" without mount point
lldap-db  |        boundary issues.
lldap-db  |
lldap-db  |        See https://github.com/docker-library/postgres/issues/37 for a (long)
lldap-db  |        discussion around this process, and suggestions for how to do so.
```bash lldap-db | Error: in 18+, these Docker images are configured to store database data in a lldap-db | format which is compatible with "pg_ctlcluster" (specifically, using lldap-db | major-version-specific directory names). This better reflects how lldap-db | PostgreSQL itself works, and how upgrades are to be performed. lldap-db | lldap-db | See also https://github.com/docker-library/postgres/pull/1259 lldap-db | lldap-db | Counter to that, there appears to be PostgreSQL data in: lldap-db | /var/lib/postgresql/data (unused mount/volume) lldap-db | lldap-db | This is usually the result of upgrading the Docker image without lldap-db | upgrading the underlying database using "pg_upgrade" (which requires both lldap-db | versions). lldap-db | lldap-db | The suggested container configuration for 18+ is to place a single mount lldap-db | at /var/lib/postgresql which will then place PostgreSQL data in a lldap-db | subdirectory, allowing usage of "pg_upgrade --link" without mount point lldap-db | boundary issues. lldap-db | lldap-db | See https://github.com/docker-library/postgres/issues/37 for a (long) lldap-db | discussion around this process, and suggestions for how to do so. ```
mg merged commit 30befc53fb into master 2025-11-28 20:43:32 +01:00
mg deleted branch containerd-snapshotter 2025-11-28 20:43:32 +01:00
mg referenced this pull request from a commit 2025-11-28 20:43:32 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mg/homeserver!739
No description provided.