Skip to content

Fix oneshot: set up file to invoke the run script - #11

Merged
dtinth merged 1 commit into
mainfrom
claude/add-ssh-server-ITHUw
May 9, 2026
Merged

dtinth merged 1 commit into
mainfrom
claude/add-ssh-server-ITHUw

Conversation

@dtinth

@dtinth dtinth commented May 9, 2026

Copy link
Copy Markdown
Owner

Summary

In s6-overlay v3, the up file for a oneshot service is an execline program that specifies what to execute — it must contain the path to the script. We left up empty, so the oneshot ran and completed instantly without doing anything, and no host keys were ever generated.

Fix: set up to contain the path to run:

/etc/s6-overlay/s6-rc.d/init-mod-dropbear/run

Verified by inspecting the actual linuxserver/docker-mods universal-cloudflared branch directly.

Test plan

  • After deploy, /config/ssh/ contains dropbear_ecdsa_host_key and dropbear_ed25519_host_key
  • svc-mod-dropbear stays running in /run/service/ instead of crash-looping
  • ssh abc@localhost works from inside the container

https://claude.ai/code/session_01XrvMKQ6TFAUnXn7Mw7dt5q


Generated by Claude Code

In s6-overlay v3, the 'up' file for a oneshot service is an execline
program specifying what to run — it must contain the path to the
script. Leaving it empty means the oneshot completes instantly without
doing anything, so no host keys were generated.

https://claude.ai/code/session_01XrvMKQ6TFAUnXn7Mw7dt5q
@dtinth
dtinth merged commit 2093ce8 into main May 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants