OpenCut-app / OpenCut-app/OpenCut
[BUG] failed to solve: failed to fetch anonymous token
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Platform
Windows 11 Pro 24H2
Browser
Firefox 140
Current Behavior
Hello. I already download Docker Desktop、bun-windows、nodejs v22.17.0.
I fork the OpenCut repository and I ran docker-compose up -d in E:\Projects\OpenCut, here what I got:
MINGW64 /e/Projects/OpenCut (main)
$ docker-compose up -d
time="" level=warning msg="The \"GOOGLE_CLIENT_ID\" variable is not set. Defaulting to a blank string."
time="" level=warning msg="The \"GOOGLE_CLIENT_SECRET\" variable is not set. Defaulting to a blank string."
[+] Building 21.6s (3/3) FINISHED
=> [internal] load local bake definitions 0.0s
=> => reading from stdin 477B 0.0s
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.22kB 0.0s
=> ERROR [internal] load metadata for docker.io/oven/bun:alpine 21.4s
------
> [internal] load metadata for docker.io/oven/bun:alpine:
------
Dockerfile:1
--------------------
1 | >>> FROM oven/bun:alpine AS base
2 |
3 | # Install dependencies and build the application
--------------------
failed to solve: failed to fetch anonymous token: Get "https://auth.docker.io/token?scope=repository%3Aoven%2Fbun%3Apull&service=registry.docker.io": dial tcp 128.242.240.212:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
View build details: docker-desktop://dashboard/build/default/default/pnc2ugefydl4viamidp4nw0de
Is this error caused by my network?
Expected Behavior
No response
Recurrence Probability
Always
Steps To Reproduce
1、git clone https://github.com/OpenCut-app/OpenCut.git
2、cd OpenCut
3、docker-compose up -d
Anything else?
No response
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 with Dockerfile line 1 and the reported docker-compose up -d reproduction on Windows 11. Check Docker Desktop's pull of oven/bun:alpine and the request to auth.docker.io, then compare the result with the listed error. Done means identifying whether the failure is project configuration or external connectivity and documenting the confirmed cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100