Unactionable error while publishing to private gitlab registry
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, typescript
Research direction
Reproduce the devcontainer features publish command from the issue with --log-level trace, focusing on the bearer-token request and subsequent tag-list request. Trace the failure far enough to expose an actionable registry error instead of only Failed to publish; done means the command reports a useful diagnostic for this private registry case.
Written by the indexing model from the issue text.
Description
Hi there. I couple of weeks ago I set up a repository of private devcontainer features on our gitlab instance and it did work pretty well.
Something has changed since then and I suspect it's probably on the side of the gitlab registry, but the error I'm getting does not allow me to investigate further, although I'm using the trace log level.
at 12:26:21 ❯ devcontainer features publish features/src --registry registry.taktsoft.com --namespace taktsoft/devcontainers/features --log-level trace
[2 ms] @devcontainers/cli 0.80.3. Node.js v22.18.0. linux 6.8.0-87-generic x64.
[2 ms] Packaging feature collection...
[3 ms] Processing feature: collection-base...
[17 ms] Processing feature: hello...
[21 ms] Processing feature: local-bin...
[25 ms] Processing feature: secure-cli...
[30 ms] Packaged 4 features!
[30 ms] Processing feature: collection-base...
[30 ms] > input: registry.taktsoft.com/taktsoft/devcontainers/features/collection-base
[30 ms] >
[30 ms] > resource: registry.taktsoft.com/taktsoft/devcontainers/features/collection-base
[30 ms] > id: collection-base
[30 ms] > owner: taktsoft
[30 ms] > namespace: taktsoft/devcontainers/features
[30 ms] > registry: registry.taktsoft.com
[30 ms] > path: taktsoft/devcontainers/features/collection-base
[30 ms] >
[30 ms] > version: latest
[31 ms] > tag?: latest
[31 ms] > digest?: undefined
[31 ms] Feature Annotations: {"dev.containers.metadata":"{\"name\":\"Taktsoft base collection\",\"id\":\"collection-base\",\"version\":\"0.0.1\",\"description\":\"A wrapper feature forcing the install of multiple other recommended features\",\"installsAfter\":[\"ghcr.io/devcontainers/features/common-utils\"],\"dependsOn\":{\"ghcr.io/devcontainers/features/common-utils:2\":{\"installZsh\":\"true\",\"username\":\"vscode\",\"userUid\":\"1000\",\"userGid\":\"1000\",\"upgradePackages\":\"true\"},\"ghcr.io/devcontainers/features/git:1\":{\"version\":\"latest\",\"ppa\":\"false\"},\"ghcr.io/stuartleeks/dev-container-features/shell-history:0\":{},\"ghcr.io/skriptfabrik/devcontainer-features/gitlab-cli:1\":{},\"registry.taktsoft.com/taktsoft/devcontainers/features/secure-cli:0.0.1\":{}}}"}
[31 ms] Fetching published versions...
[128 ms] [httpOci] Attempting to authenticate via 'Bearer' auth.
[129 ms] [httpOci] Found auths entry in '/home/max/.docker/config.json' for registry 'registry.taktsoft.com'
[129 ms] [httpOci] Attempting to fetch bearer token from: https://git.taktsoft.com/jwt/auth?service=container_registry&scope=repository:taktsoft/devcontainers/features/collection-base:pull
[428 ms] [httpOci] 200 on reattempt after auth: https://registry.taktsoft.com/v2/taktsoft/devcontainers/features/collection-base/tags/list
[428 ms] (!) ERR: Failed to publish 'registry.taktsoft.com/taktsoft/devcontainers/features/collection-base'
It tries to get the tag list, but then only fails with
[428 ms] (!) ERR: Failed to publish 'registry.taktsoft.com/taktsoft/devcontainers/features/collection-base'
Any idea on how I can get even more details about the error than just the trace log level?
Any help is much appreciated! ❤️
p.s.
We had to change the s3 backend for gitlab and decided to start with a completely empty registry instead of migrating the old bucket. No I idea if this could cause problems, but for other artifacts the registry works just fine.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 461
- Avg merge
- 18m
- Merged PRs (30d)
- 5
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 devcontainers/cli
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
devcontainers/cli#1203 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
devcontainers/cli#1178 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
devcontainers/cli#1308 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
devcontainers/cli#1307 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
devcontainers/cli#1305 ·
All issues in devcontainers/cli
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100