Issues
- Docker images built from Dockerfile are brokenPBM-1142Resolved issue: PBM-1142
- PBM 2.1.0 crashes mongod node when using incremental physical backupsPBM-1136Resolved issue: PBM-1136Jean da Silva
- Support the virtual-hosted-style for s3 storage bucketsPBM-1133Resolved issue: PBM-1133Dmytro Zghoba
- Adds an option to delete backups based on its typePBM-1127Resolved issue: PBM-1127
- PBM 2.1 could fail to restore backup 1.7PBM-1124Resolved issue: PBM-1124Dmytro Zghoba
- PBM restore takes long timePBM-1120Resolved issue: PBM-1120Dmytro Zghoba
- Unexpected behaviour on pitr restore out of rangePBM-1109Resolved issue: PBM-1109
- New storage config and force-resync in the same commandPBM-1107
- Failed to refresh session cache after physical restorePBM-1102Resolved issue: PBM-1102andrew.pogrebnoi
- New FCV message introduced in 2.1.0 should not be an error.PBM-1101Resolved issue: PBM-1101
Docker images built from Dockerfile are broken
Description
Environment
Activity
Dmytro ZghobaJuly 9, 2023 at 3:21 PM
for now please do not changes other images except "docker/*". changes in e2e-tests require testing and fixing them.
does it require to use ubi for testing? I just do not know what we will win if we will start use them in automation tests
Damiano AlbaniJuly 9, 2023 at 2:39 PM
Hum, I meant bullseye obviously, not buster.
And now that I read the full content of https://github.com/percona/percona-backup-mongodb/pull/840, I think my own PR is missing some bits in the E2E and Github Workflows parts.
Damiano AlbaniJuly 9, 2023 at 2:36 PM
Oh, I think I missed the last commit in the repository upgrading the base image to golang:1.19-buster.
You may want to implement differently than how you did though, by staying in the same ubi8 ecosystem.
Where the benefit is that the (binary) compatibility is guaranted and there won't be any silent breakage in the future.
See my proposal at https://github.com/percona/percona-backup-mongodb/pull/853 if you're interested.
Dmytro ZghobaJuly 9, 2023 at 2:32 PMEdited
FYI we changed base golang image in all Dockerfiles in the repo to “golang:1.19-bullseye”. since 2.2.0 it will be affected
After having built the Docker for Kubernetes using https://github.com/percona/percona-backup-mongodb/blob/main/docker/Dockerfile.k8s and configured my PSMDB instance to use it, I got the following error message at startup of the container:
I haven't checked if https://github.com/percona/percona-backup-mongodb/blob/main/docker/Dockerfile is affected, but I suppose so since their definition is very similar.
I suppose the issue comes up only now due to change in the
golang:1.19base image.