microsoft / microsoft/planetary-computer-apis
setup script requires private images
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 129
- Forks
- 33
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 1
Description
I tried running the setup script per the instructions, but its failing because some of the images are private, e.g. pc-apis-tiler-dev internal
$ ./scripts/setup
==Building images...
[+] Building 5.0s (22/30)
=> [pc-apis-nginx internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 32B 0.0s
=> [pc-apis-tiler internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.39kB 0.0s
=> [pc-apis-stac-dev internal] load build definition from Dockerfile.dev 0.0s
=> => transferring dockerfile: 192B 0.0s
=> [pc-apis-tiler-dev internal] load build definition from Dockerfile.dev 0.0s
=> => transferring dockerfile: 194B 0.0s
=> [pc-apis-funcs internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 627B 0.0s
=> [pc-apis-stac internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 32B 0.0s
=> [pc-apis-stac-db internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 32B 0.0s
=> [pc-apis-nginx internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.0s
=> [pc-apis-tiler internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [pc-apis-stac-dev internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [pc-apis-tiler-dev internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.0s
=> [pc-apis-funcs internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [pc-apis-stac internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [pc-apis-stac-db internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> CANCELED [pc-apis-nginx internal] load metadata for docker.io/library/nginx:1.10 4.5s
=> CANCELED [pc-apis-tiler internal] load metadata for docker.io/library/python:3.9-slim 4.4s
=> CANCELED [pc-apis-stac-dev internal] load metadata for docker.io/library/pc-apis-stac:latest 4.4s
=> ERROR [pc-apis-tiler-dev internal] load metadata for docker.io/library/pc-apis-tiler:latest 4.3s
=> [pc-apis-funcs internal] load metadata for mcr.microsoft.com/azure-functions/python:4-python3.8 0.3s
=> CANCELED [pc-apis-stac-db internal] load metadata for docker.io/library/postgres:13 4.3s
=> CANCELED [pc-apis-funcs 1/9] FROM mcr.microsoft.com/azure-functions/python:4-python3.8@sha256:89a82768164b22834854b97c194aff9d4494d26969f3673fe4b3a462c36236 4.1s
=> => resolve mcr.microsoft.com/azure-functions/python:4-python3.8@sha256:89a82768164b22834854b97c194aff9d4494d26969f3673fe4b3a462c3623682 0.0s
=> => sha256:7ae7bb2a534b251b3501f6c25d5f154e848e923441e08454f10dfaa75d62dfdb 10.05kB / 10.05kB 0.0s
=> => sha256:a603fa5e3b4127f210503aaa6189abf6286ee5a73deeaab460f8f33ebc6b64e2 7.34MB / 31.41MB 4.2s
=> => sha256:b00aaacf759c581712fa578a6b4e8e0b9fc780919a5d835a168457b754755644 1.08MB / 1.08MB 1.1s
=> => sha256:372d780866a7e569457582348fbf850edc018b6b015335a4a56403fe299ff04b 7.34MB / 11.34MB 4.2s
=> => sha256:89a82768164b22834854b97c194aff9d4494d26969f3673fe4b3a462c3623682 2.43kB / 2.43kB 0.0s
=> => sha256:feb836cf9ff261a0d9feb57f8808540cbb140d6d9e957af5daad2767d65fec36 232B / 232B 1.3s
=> => sha256:6a0e4abca74a97205cba7ecb141fd4210bfab67dddb55e3a1fdaa6bcefbc44de 3.18MB / 3.18MB 3.0s
=> => sha256:f185cb5182255c6a037ffb84ac09b3826bebf5f56ed56c2ea08d3ac5211120eb 1.05MB / 131.85MB 4.2s
=> [pc-apis-funcs internal] load build context 0.1s
=> => transferring context: 1.93kB 0.0s
------
> [pc-apis-tiler-dev internal] load metadata for docker.io/library/pc-apis-tiler:latest:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by running scripts/setup and inspect the Dockerfile and Dockerfile.dev references for pc-apis-tiler-dev and the other pc-apis images. Trace which image names are built locally versus pulled from Docker Hub. Done means a fresh setup can build or access all required images without private-image authorization errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100