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

Advice for how to debug startup issues

未关闭
  • 哪里不对？
#259 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
docker, github-actions, linux, node.js, typescript, ubuntu
领域
ci-cd, devops, infrastructure

调研方向

从自托管的 Ubuntu 22.04 runner 上记录的 devcontainer up 调用和底层的 docker start 命令开始；捕获 Docker 的 stderr，并将其与成功的 build 阶段进行比较。完成的标准是找出可复现的原因，或记录解释启动失败所需的、特定于该 runner 的诊断步骤。

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

描述

I'm trying to debug a new startup error we're seeing in a self-hosted GitHub Actions CI runner (Linux X64 ubuntu-22.04). This workflow has been running great for weeks (we've been loving the devcontainers/ci action!), but all of a sudden it refuses to work. The error is really opaque (to me):

🏃 start container
  About to run devcontainer up --workspace-folder /home/github/actions-runner/_work/DeepStructure/DeepStructure --remote-env GITHUB_OUTPUT=/mnt/github/output --remote-env GITHUB_ENV=/mnt/github/env --remote-env GITHUB_PATH=/mnt/github/path --remote-env GITHUB_STEP_SUMMARY=/mnt/github/step-summary --mount type=bind,source=/home/github/actions-runner/_work/_temp/_runner_file_commands/set_output_39dffcd4-c68e-4716-9ada-e377f11f5af8,target=/mnt/github/output --mount type=bind,source=/home/github/actions-runner/_work/_temp/_runner_file_commands/set_env_39dffcd4-c68e-4716-9ada-e377f11f5af8,target=/mnt/github/env --mount type=bind,source=/home/github/actions-runner/_work/_temp/_runner_file_commands/add_path_39dffcd4-c68e-4716-9ada-e377f11f5af8,target=/mnt/github/path --mount type=bind,source=/home/github/actions-runner/_work/_temp/_runner_file_commands/step_summary_39dffcd4-c68e-4716-9ada-e377f11f5af8,target=/mnt/github/step-summary
  [2023-11-02T00:48:54.924Z] @devcontainers/cli 0.52.1. Node.js v20.8.1. linux 5.15.0-1045-kvm x64.
  
  Error: Command failed: docker start 2252cc6b00073132e1ddd4ebfa2931bdc8f9e759d63446c07a4e1e7537ea6dfd
      at EAA (/home/github/actions-runner/_work/_tool/node/20.8.1/x64/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:462:1260)
      at kK (/home/github/actions-runner/_work/_tool/node/20.8.1/x64/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:462:1002)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async NAA (/home/github/actions-runner/_work/_tool/node/20.8.1/x64/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:479:3660)
      at async vC (/home/github/actions-runner/_work/_tool/node/20.8.1/x64/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:479:4775)
      at async etA (/home/github/actions-runner/_work/_tool/node/20.8.1/x64/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:613:10941)
      at async AtA (/home/github/actions-runner/_work/_tool/node/20.8.1/x64/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:613:10682)
  
  Error: Dev container up failed: Command failed: docker start 2252cc6b00073132e1ddd4ebfa2931bdc8f9e759d63446c07a4e1e7537ea6dfd (exit code: undefined)
  An error occurred setting up the container.
  Error: Command failed: docker start 2252cc6b00073132e1ddd4ebfa2931bdc8f9e759d63446c07a4e1e7537ea6dfd

The build stage that precedes this completes without issue, but for whatever reason it dies trying to start a container. I also know it isn't a disk space issue.

We can't reproduce locally, so it's something about this CI environment I guess. Any advice on how to dig into this deeper?

主要语言
TypeScript
星标
499
派生
101
30 天内没有已合并 PR

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

devcontainers/ci 的其他 Issue

查看 devcontainers/ci 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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