Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[docs-scanner] Unclear relationship between sandbox:use PAT permission and granular account permissions

未关闭 适合新手
  • 哪里不对？
#26,225 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
88/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker
领域
documentation

调研方向

打开 content/manuals/ai/sandboxes-api/authentication.md 并阅读“Authenticate automation with a PAT”和“Resource access and permissions”部分。明确 PAT 作用域 sandbox:use 与 sandboxesCreate、sandboxesRead 和 sandboxesDelete 的关系，包括两项检查都会影响每个请求。确认文档说明了如何诊断权限失败。

由索引模型根据 Issue 内容生成。

描述

File: content/manuals/ai/sandboxes-api/authentication.md

Issue

The authentication documentation describes two different permission concepts without explaining their relationship:

  1. PAT scope: "When creating the token, select the sandbox:use permission in your Docker account's personal access token settings."

  2. Account permissions: "Each request also checks whether you have permission for the action on the target resource. For example, creating a sandbox requires sandboxesCreate, reading it requires sandboxesRead, and deleting it requires sandboxesDelete."

The document never clarifies:

  • Does the sandbox:use PAT scope grant all the granular permissions (sandboxesCreate, sandboxesRead, etc.)?
  • Are the granular permissions separate account-level settings that must also be configured?
  • If a PAT has sandbox:use but the account lacks sandboxesCreate, what happens?
Why this matters

A reader setting up authentication needs to know:

  • Whether selecting sandbox:use is sufficient for all sandbox operations
  • Whether additional account configuration is required beyond creating the PAT
  • How to diagnose permission errors (is it the PAT scope or the account permission?)

The current text suggests these are related but doesn't explain the relationship, leaving readers uncertain whether they've completed the setup correctly.

Suggested fix

Add a clarifying sentence in the "Authenticate automation with a PAT" section:

When creating the token, select the sandbox:use permission in your Docker account's personal access token settings. This scope grants access to all sandbox operations, subject to your account's permissions. The API checks both the PAT scope and your account permissions for each request.

Or add a subsection under "Resource access and permissions" that explicitly states:

The sandbox:use PAT scope authorizes your application to act on your behalf. Your account's permissions (sandboxesCreate, sandboxesRead, etc.) then determine which operations succeed. Both the PAT scope and the account permission must allow the action.

Found by nightly documentation quality scanner

主要语言
Markdown
星标
4.7k
派生
8.5k
平均合并
1 天 18 小时
30 天内合并 PR
127

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

docker/docs 的其他 Issue

查看 docker/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。