Use postgres alpine images to add support for PG 17

[miharekar]

Postgres publishes alpine versions of Docker images including for PG 17 which was recently released.

So this approach should work better than #60 where we're left to the mercy of Alpine releases 😅

[lesha-co]

so uh @ledermann do you plan to merge this PR or that other one?

You've mentioned that this is a good way to handle things so why not move forward with this?

[ledermann]

@lesha-co I can't decide, @eeshugerman is the owner and maintainer of this repo.

[ak4zh]

While we are waiting for this to be merged, is there a way to use it already. @miharekar Is there a public docker image with these changes applied for v17 ?

I have always used this utility for all my postgres backups, and now I have a production project running with postgres 17 just to realise later that this tool is not yet updated to support v17 yet.

[miharekar]

@ak4zh I have my own fork and I've just yesterday uploaded it with 17.2 image: https://hub.docker.com/repository/docker/mrfoto/postgres-backup-s3/general

I use it for my own needs, so no guarantees 😅 Maybe best you fork it yourself. If I managed to do it, you know it isn't that hard 😂

[ak4zh]

@miharekar Thanks, I will see if I can figure out the docker image publishing part myself. Forking is fine but I haven’t explored the docker image publish part before, I suppose I need to signup as publisher in docker-hub or something, will give it a try today so I can reuse the image.

[lesha-co]

You don't really need to go into trouble of publishing anything just for this one case.

What I did is added this repo as a submodule at commit 101949343a3eb3187e61965289b82d8e42acbd5e (i.e. this pull request's head)

then added a build (rather than an image) entry to docker-compose file

services:
  backup:
    build:
      context: ./postgres-backup-s3
      args:
        - POSTGRES_VERSION=17
    environment:
      - SCHEDULE
      - ...

and that's it.

when, if ever, this pr gets merged, I'll either just remove the submodule and use the newly available version from registry, or just change the submodule head or more likely just do nothing because why fixing something that isn't broken

[ahmayou]

@lesha-co I can't decide, @eeshugerman is the owner and maintainer of this repo.

@eeshugerman can you please merge this PR?

[ak4zh]

@miharekar It seems the docker hub has only arm version not for any other arch like amd64 I am trying to deploy it with caprover so can't deploy directly through docker-compose.

[miharekar]

@ak4zh yeah, like I said - I built it for my own needs. Feel free to build one yourself

[ledermann]

Because this repo seems to be not maintained anymore, I have created a fork and merged this PR. I have no plans to extend the tool any further. My only concern is to ensure that it works with current PostgreSQL versions.

I have set up GitHub Actions to push the Docker images to ghcr.io for arm64 and amd64.

The fork repo:

• https://github.com/solectrus/postgres-s3-backup (Name changed to match another backup repository in my organization)

Docker images:

• ghcr.io/solectrus/postgres-s3-backup:17
• ghcr.io/solectrus/postgres-s3-backup:16
• ghcr.io/solectrus/postgres-s3-backup:15
• ghcr.io/solectrus/postgres-s3-backup:14
• ghcr.io/solectrus/postgres-s3-backup:13

Thanks to @eeshugerman for creating this repo and to @miharekar for this PR!

[TRRC62]

@ledermann You forked the project without any plans to extend or contribute, yet you’ve added a Ko-fi link for support—profiting off someone else's work.

[ledermann]

@TRRC62 My plan for this fork is to keep the Docker image compatible with the latest PostgreSQL versions - something many people here have been looking for. I believe that’s a good enough reason to fork an unmaintained repo.

I created the fork under my organization @solectrus, which is an open-source project with a donation button. I didn’t realize that new repositories automatically inherit this button. That was an oversight, and I’ve now disabled it for this repo. Of course, I never intended to make money from someone else’s work.

I made the fork public because I thought it could be useful to others. If the only feedback is criticism that I have no further plans, maybe I shouldn’t have shared it at all.

[jspooner]

@ledermann thanks for sharing this as I'm using 17!