Skip to content
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.

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

Docker images platform information can impact usage #153

Open
zacharyDez opened this issue Oct 26, 2023 · 6 comments
Open

Docker images platform information can impact usage #153

zacharyDez opened this issue Oct 26, 2023 · 6 comments
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@zacharyDez
Copy link
Contributor

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

  • Apple M2, MacOS 14.0
  • Docker Desktop 4.25.0
@zacharyDez zacharyDez added bug Something isn't working good first issue Good for newcomers labels Oct 26, 2023
@zacharyDez zacharyDez self-assigned this Oct 26, 2023
@zacharyDez
Copy link
Contributor Author

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
Copy link
Member

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
Copy link
Contributor Author

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

@batpad
Copy link
Member

batpad commented Nov 9, 2023

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
Copy link
Member

@batpad just add platform: linux/amd64 in each services #153 (comment)

@batpad
Copy link
Member

batpad commented Nov 9, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants