Skip to content

fix: Use exact version number for postgress #243

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 30, 2025
Merged

fix: Use exact version number for postgress #243

merged 1 commit into from
Sep 30, 2025

Conversation

teogeb
Copy link
Contributor

@teogeb teogeb commented Sep 30, 2025 •
edited
Loading

Before this PR the postgres service didn't specify any version number. I.e. used the latest version . When v18 was released on 2025-09-25, we started to get this error in network monorepo's GitHub action logs:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/docker/volumes/streamr-docker-dev_data-postgres-fastchain/_data" to rootfs at "/var/lib/postgresql/data": change mount propagation through procfd: open o_path procfd: open /var/lib/docker/overlay2/1064c70ea0d33db456a30333bef5a49e1cbf1a98b4d097def04149a63bca145f/merged/var/lib/postgresql/data: no such file or directory: unknown
streamr-docker-dev: error while running command: "docker compose --ansi never -f docker-compose.yml  -f docker-compose-ci.yml up  -d --remove-orphans cassandra init-keyspace dev-chain-fast deploy-network-subgraphs-fastchain broker-node-storage-1 entry-point "

Most likely there is some incompatibility with v18. As v17 worked ok, we use that version now in docker-compose.yml.

@teogeb teogeb requested a review from juslesan September 30, 2025 10:00
@teogeb teogeb merged commit 165811d into master Sep 30, 2025
3 checks passed
@teogeb teogeb deleted the use-exact-version-number-for-postgres branch September 30, 2025 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@juslesan juslesan juslesan approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@teogeb @juslesan