search

timescale / timescaledb-docker-ha

Create Docker images containing TimescaleDB, Patroni to be used by developers and Kubernetes.
Apache License 2.0
143 stars 38 forks source link

[Bug]: timescale/timescaledb-ha:pg16 not working on macOS (Macbook M1) #449

Closed gitmalong closed 2 months ago

gitmalong commented 4 months ago

What type of bug is this?

Other

What subsystems and features are affected?

Other

What happened?

FROM timescale/timescaledb-ha:pg16-all

--> 

[+] Building 0.7s (2/2) FINISHED                                                            docker:desktop-linux
 => [db internal] load build definition from Dockerfile                                                     0.0s
 => => transferring dockerfile: 1.91kB                                                                      0.0s
 => ERROR [db internal] load metadata for docker.io/timescale/timescaledb-ha:pg16-all                       0.7s
------
 > [db internal] load metadata for docker.io/timescale/timescaledb-ha:pg16-all:
------
failed to solve: timescale/timescaledb-ha:pg16-all: no match for platform in manifest: not found

TimescaleDB version affected

latest

PostgreSQL version used

latest

What operating system did you use?

macOS 14.2.1

What installation method did you use?

Docker

What platform did you run on?

On prem/Self-hosted

Relevant log output and stack trace

No response

How can we reproduce the bug?

see above
graveland commented 3 months ago

Currently the master branch of the timescaledb-docker-ha repository can't build arm64 images. If you're using a FROM statement on a dockerfile that bases itself off of -ha, you're going to have to build it with --platform linux/amd64 to pull the available amd64 image.

There is a development branch for arm64 at brent/base_arm64 that publishes images to a different location: if you use FROM timscaledev/timescaledb-ha:pg16-all in your dockerfile it should be able to pick up the arm64 build. Let me know if that fixes your problem, or if there are any other issues!

graveland commented 2 months ago

Should be fixed as of #456