starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

bash, dash ash or whatever shell on docker container #375

New Issue
Closed
opened 2025-12-29 01:27:54 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:27:54 +01:00
Owner
Copy Link

Originally created by @Rugaliz on GitHub (Nov 22, 2022).

So I'm running the docker version and sometimes I need to run some commands that require a response.
I can't seam to run any of the popular shells on the docker version (I'm using the latest docker container BTW), dunno if I missed something but the installation docks don't give much insight on what is available.

Is it possible to modify the latest container image to feature a common shell?

Cheers

Originally created by @Rugaliz on GitHub (Nov 22, 2022). So I'm running the docker version and sometimes I need to run some commands that require a response. I can't seam to run any of the popular shells on the docker version (I'm using the latest docker container BTW), dunno if I missed something but the installation docks don't give much insight on what is available. Is it possible to modify the latest container image to feature a common shell? Cheers
adam added the enhancement label 2025-12-29 01:27:54 +01:00
adam closed this issue 2025-12-29 01:27:54 +01:00
adam commented 2025-12-29 01:27:55 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 24, 2022):

Hi

I wanted to keep this, but we had some people insisting this was bad practice and we should not have it in the container. I disagree and only use the Dockerfile marked with Debug since it contains a shell.

I suspect I will ditch the current Dockerfile at some point in the future in favour of our build system, I'll keep this in mind to fix it.

In the meantime, I would use the Debug image if you need shell. Sorry for the inconvenience.

For reference, this is the discussion changing the container images: https://github.com/juanfont/headscale/pull/214
at the time, we gave in to the arguments, but they have been deemed highly impractical and when we have some time, we will revert this. Life is to short to deal with this.

@kradalby commented on GitHub (Nov 24, 2022): Hi I wanted to keep this, but we had some people insisting this was bad practice and we should not have it in the container. I disagree and only use the `Dockerfile` marked with Debug since it contains a shell. I suspect I will ditch the current Dockerfile at some point in the future in favour of our build system, I'll keep this in mind to fix it. In the meantime, I would use the Debug image if you need shell. Sorry for the inconvenience. For reference, this is the discussion changing the container images: https://github.com/juanfont/headscale/pull/214 at the time, we gave in to the arguments, but they have been deemed highly impractical and when we have some time, we will revert this. Life is to short to deal with this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#375
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?