Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

sharkymark/templates/docker-claude: workspaces start with an error because tmux is not installed

Abierto
  • ¿Algo no está bien?
#1,186 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
bash, docker, terraform
Área
devops

Línea de trabajo

Start by reading the setup_script preset and the base image configuration for registry/sharkymark/templates/docker-claude; the report identifies a failed apt-get update that prevents tmux from being installed. Check how the setup handles command failures and reproduce the workspace startup error. Done means a new workspace starts the app in tmux and the preview on port 4200 is healthy.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

New workspaces from registry/sharkymark/templates/docker-claude start with an error ("agent startup script exited with an error"), and the "Preview your app" app stays unhealthy. I found this while testing #1180 on a live workspace. The cause is in the template's setup_script preset and the base image, not in #1180, so it stays after #1180 merges.

Startup error and broken Preview app

  1. codercom/example-universal:ubuntu includes a Yarn apt repository whose signing key is missing, so sudo apt-get update fails:

    W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.

  2. The setup_script preset runs sudo apt-get update && sudo apt-get install -y tmux. Because the update fails, && skips the install, and tmux is never installed.

  3. The demo repo's start-dev.sh starts the app in tmux sessions, so it fails with ./start-dev.sh: line 106: tmux: command not found. The dev server on port 4200 never starts.

The Ubuntu repositories update correctly, and only the Yarn repository fails. Running sudo apt-get install -y tmux by itself succeeds, and after that start-dev.sh exits 0 and port 4200 returns 200.

Possible fixes:

  • Do not let a failed update block the install: sudo apt-get update || true, then sudo apt-get install -y tmux.
  • Fix or remove the broken Yarn repository in the image so that apt-get update succeeds.

Other issues

  • Chrome for the Playwright MCP server is not installed. npx playwright install chrome also runs apt-get update and fails with Error: Failed to install chrome. The playwright MCP server still shows as connected. I did not check whether its browser tools work without Chrome.
  • Setup script errors are hidden. The script has no set -e, so failures partway through are ignored. Only the last command's exit code counts, so the problem only shows up at the end, at tmux.
  • Modules are not pinned. coder-login, dotfiles, code-server, and git-config have no version, so every build uses the latest release.
  • README typo. "Claude CodeAI agent" appears in the frontmatter description and in the body.
  • preview_port default does not match the app. The parameter defaults to 3000, but the app runs on 4200. The default preset sets 4200, so this only matters without the preset.
  • Cosmetic leftovers in main.tf. The comment "Use the docker gateway if the access URL is 127.0.0.1" appears twice (once above a commented-out entrypoint), and the agent startup_script is an empty #!/bin/sh.

How it was found

The template was pushed with the #1180 changes (claude-code module 5.5.1) and a workspace was created from the default preset. The evidence comes from ~/.coder-modules/coder/claude-code/logs/post_install.log and from commands run in the workspace. The setup script and image are the same on main.

Generated with Coder Agents.

Lenguaje dominante
HCL
Estrellas
81
Forks
169
Merge medio
3 d 7 h
PR fusionados (30 d)
29

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de coder/registry

Todos los issues de coder/registry

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.