search

developmentseed / eoAPI

[Active Development] Earth Observation API (Metadata, Raster and Vector services)
https://eoapi.dev
MIT License
191 stars 20 forks source link

Docker images platform information can impact usage #153

Open zacharyDez opened 8 months ago

zacharyDez commented 8 months ago

Problem description

Since upgrading Docker desktop locally, I was unable to pull the database image:

docker compose up
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string. 
[+] Running 0/1
 ⠼ database Pulling                                                                                                                                             1.4s 
no matching manifest for linux/arm64/v8 in the manifest list entries

Expected Output

An eoAPI end-user can run docker compose up and have a running instance regardless of their local machine.

Environment Information

zacharyDez commented 8 months ago

The tags on the pgstac images show that arm64/v8 is absent. I do not know if previous versions of docker-compose would default to the unknown tag, but it is not currently.

A solution could be to define the platform in the docker-compose file for the database (tested locally). But it seems an inefficient and un-recommend solution. @bitner @vincentsarago, any insights on how we should address this? Is it simple to add another tag to the pgstac image repository?

vincentsarago commented 8 months ago

you may have to add https://github.com/developmentseed/eoAPI/blob/main/docker-compose.yml#L45 in your docker-compose.yml file but I don't think we want that by default

This should be solve once we update the new pgstac image (if we create a linux/arm64/v8 image).

I'm afraid all the other images weren't built for linux/arm64/v8 anyway 😭 but they will at one point!

zacharyDez commented 8 months ago

Yes, exactly! Ok, I will keep the issue open to track progress.

batpad commented 8 months ago

Am bumping into this as well 😢 were you able to find a work-around to get docker compose up to work on an m1 @zacharyDez ?

vincentsarago commented 8 months ago

@batpad just add platform: linux/amd64 in each services https://github.com/developmentseed/eoAPI/issues/153#issuecomment-1781561265

batpad commented 8 months ago

Ah my bad - this seems to work, thank you @vincentsarago 🙏