You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recall ash (alpines default) possibly not playing nicer with bashishms. So I am wondering if this block is actually compatible with sh, or has something that only works in bash?. I've noticed most symlinked bashes to /bin/sh usually just run it as bash, not as sh
Also of note: overrideCommand: false seems ignored for compose files, unsure why that is, or if it's related, but makes it a bit difficult to force it to work. I have made this work in other containers though, so it's usually work-around able, but its strange behaviour to be sure
The text was updated successfully, but these errors were encountered:
command: sleep infinity in the compose file fixes it. Though strange as not in compose, this is not required.
For others who find this, overrideCommand is misleading, it seems to always inject its own stuff, but overrideCommands behaviour is whether it still calls the original entry points or not it seems. It probably should be named 'disableDefaultEntrypoint' rather than override, as it seems that's its purpose.
I've solved this for me, but will leave it open in case the devs want to understand the compose/vs container differences, if not I imagine a GitHub bot will auto-close this at some point :)
You could use "overrideCommand": true instead of command: sleep infinity. overrideCommand is false for Docker Compose for historical reasons, it is true for single containers.
Version: 1.95.3 (Universal)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0
Steps to Reproduce:
Likely cause:
Devcontainers override entry point and command, this is good!.
I recall ash (alpines default) possibly not playing nicer with bashishms. So I am wondering if this block is actually compatible with sh, or has something that only works in bash?. I've noticed most symlinked bashes to /bin/sh usually just run it as bash, not as sh
Also of note: overrideCommand: false seems ignored for compose files, unsure why that is, or if it's related, but makes it a bit difficult to force it to work. I have made this work in other containers though, so it's usually work-around able, but its strange behaviour to be sure
The text was updated successfully, but these errors were encountered: