1. 验证密钥是否已设置：eve secrets list --project proj_xxx
2. 如果使用自定义 BYO 注册表，请验证凭据是否映射到 registry.host
3. 确认清单中的 imagePull 元数据正确
4. 在 Dockerfile 中添加 OCI 源标签：LABEL org.opencontainers.image.source="https://github.com/ORG/REPO"

某些注册表需要与仓库链接的包元数据或工作区级别的认证对齐。

构建失败

症状

• 流水线在构建步骤失败
• eve build diagnose 显示运行状态为 failed

排查

eve build list --project <id>          # 查找最近的构建
eve build diagnose <build_id>          # 完整状态转储
eve build logs <build_id>              # 原始构建输出

常见原因

注册表认证：

• 如果使用自定义注册表模式，请验证 REGISTRY_USERNAME 和 REGISTRY_PASSWORD 密钥是否已设置（或提供等效的注册表凭据）。使用托管注册表（registry: "eve"）时，通常不需要此步骤。
• 确保凭据可以访问配置的注册表账户和命名空间
• 检查：eve secrets list --project <id>

Dockerfile 问题：

• 服务的清单中必须包含指向包含 Dockerfile 目录的 build.context
• Dockerfile 路径默认为 <context>/Dockerfile
• 多阶段构建适用于 BuildKit；使用 Kaniko 时可能失败

工作区/克隆错误：

• 构建需要在正确的 git SHA 处的工作区
• 检查 eve build diagnose 中是否有工作区准备错误

镜像推送失败：

• OCI 标签有助于将包链接到仓库：在 Dockerfile 中添加 LABEL org.opencontainers.image.source="https://github.com/OWNER/REPO"
• 使用 BYO/自定义注册表时，确保注册表主机和认证与清单中的 registry.host 匹配

作业卡住或阻塞

eve job show <job-id>
eve job dep list <job-id>

如果合适，使用 eve job update 解决依赖关系或更新阶段。

部署后应用无法访问

• 确认部署作业成功（eve job result）。
• 验证入口主机模式：{service}.{orgSlug}-{projectSlug}-{env}.{domain}。
• 确保服务端口与 x-eve.ingress.port 匹配。

问题升级

如果 CLI 输出不足，请收集：

• eve system health
• eve job diagnose <job-id>
• 清单差异（最近的更改）

然后移交给平台操作员。

每周安装次数

149

仓库

incept5/eve-skillpacks

首次出现

2026年2月8日

安全审计

Gen Agent Trust HubPassSocketPassSnykPass

安装于

gemini-cli149

codex149

claude-code146

pi53

github-copilot32

kimi-cli32

If build jobs fail with UNAUTHORIZED: authentication required when pushing:

1. Verify secrets are set: eve secrets list --project proj_xxx
2. If using a custom BYO registry, verify credentials map to registry.host
3. Confirm the imagePull metadata in your manifest is correct
4. Add OCI source label to Dockerfile: LABEL org.opencontainers.image.source="https://github.com/ORG/REPO"

Some registries require repository-linked package metadata or workspace-level auth alignment.

Build Failures

Symptoms

• Pipeline fails at build step
• eve build diagnose shows run status = failed

Triage

eve build list --project <id>          # Find recent builds
eve build diagnose <build_id>          # Full state dump
eve build logs <build_id>              # Raw build output

Common Causes

Registry authentication:

• If using custom registry mode, verify REGISTRY_USERNAME and REGISTRY_PASSWORD secrets are set (or provider-equivalent registry credentials). With managed registry (registry: "eve"), this step is usually not required.
• Ensure credentials can access the configured registry account and namespace
• Check: eve secrets list --project <id>

Dockerfile issues:

• Service must have build.context in manifest pointing to directory with Dockerfile
• Dockerfile path defaults to <context>/Dockerfile
• Multi-stage builds work with BuildKit; may fail with Kaniko

Workspace/clone errors:

• Build requires workspace at the correct git SHA
• Check eve build diagnose for workspace preparation errors

Image push failures:

• OCI labels help link packages to repos: add LABEL org.opencontainers.image.source="https://github.com/OWNER/REPO" to Dockerfile
• Ensure registry host and auth match manifest registry.host when using BYO/custom registry

Job Stuck or Blocked

eve job show <job-id>
eve job dep list <job-id>

Resolve dependencies or update phase with eve job update if appropriate.

App Not Reachable After Deploy

• Confirm deploy job succeeded (eve job result).
• Validate ingress host pattern: {service}.{orgSlug}-{projectSlug}-{env}.{domain}.
• Ensure service port matches x-eve.ingress.port.

Escalation

If CLI output is insufficient, collect:

• eve system health
• eve job diagnose <job-id>
• manifest diff (recent changes)

Then hand off to the platform operator.

Weekly Installs

149

Repository

incept5/eve-skillpacks

First Seen

Feb 8, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

gemini-cli149

codex149

claude-code146

pi53

github-copilot32

kimi-cli32