Docker compose file references database manifest
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- docker, docker-compose
- Domain
- devops
Research direction
Start in docker-compose.yml at line 134, where the database image is configured. Run docker compose up on an Apple M1 or another linux/arm64 environment to reproduce the manifest error. Done means the compose file uses an image manifest available for the target architecture and the database pulls successfully.
Written by the indexing model from the issue text.
Description
Problem description
Currently the docker compose file uses the following database image:
image: ghcr.io/stac-utils/pgstac:v0.8.1
which causes the following error:
docker compose up
[+] Running 0/1
⠋ database Pulling 0.9s
no matching manifest for linux/arm64/v8 in the manifest list entries
Incrementing the image to the following works:
image: ghcr.io/stac-utils/pgstac:v0.8.2
Expected Output
I would expect that the database image would be available for my architecture.
Environment Information
macOS Sonoma 14.3.1
Chip: Apple M1 Max
- Dominant language
- Shell
- Stars
- 330
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from developmentseed/eoAPI
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
developmentseed/eoAPI#224 ·
-
developmentseed/eoAPI#229 · 1 comment · 1 reaction · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
developmentseed/eoAPI#215 · 1 reaction ·
-
Feature Request
developmentseed/eoAPI#193 · 5 comments · 1 assignee ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
developmentseed/eoAPI#191 · 1 comment · 1 reaction ·
All issues in developmentseed/eoAPI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100