I have some problems with devcontainer.

My setup is simple, .devcontainer folder with devcontainer.json:

    "name": "Ubuntu",
    "build": {
        "dockerfile": "Dockerfile"
    "extensions": [ "nadako.vshaxe" ],
    "forwardPorts": [ 3000 ],
    "remoteUser": "vscode"

And Dockerfile:

FROM haxe:4.2-bullseye


RUN groupadd --gid $USER_GID $USERNAME && \
    useradd \
      --uid ${USER_UID} \
      --gid ${USER_GID} \
      --create-home \
      --shell /bin/bash \

RUN apt-get upgrade && \
    apt-get update

RUN haxelib setup ~/haxelib && \
    haxelib install lime && \
    haxelib install openfl

CMD ["sh", "-c"]

However it does not work properly: Workspace got mangled

Additionally I can't get any logs, as trying to open the terminal results in

The terminal process failed to launch: Starting directory (cwd) "/workspaces/e9d1a4e0e6c117e14accaa9eff92c0d10446e1eb5f284b3c9438541c20734591" does not exist.
  • Have you tried to create a folder e9d1a4e0e6c117e14accaa9eff92c0d10446e1eb5f284b3c9438541c20734591 within your workspaces folder? The gui has a yellow ! indicating the issue
    – Ramhound
    May 14 at 8:34
  • The hash-named folder is created correctly in a different setup by devcontainer wrapper docker image I presume. It has to work automatically
    – Misiur
    May 14 at 9:34
  • 1
    When you hit "Open Workspace" and select a workspace that does exist what happens? Something in your setup is not working, obviously, because VS believes the workspace does not exist.
    – Ramhound
    May 14 at 9:37
  • That was a good advice, it does in fact open now a differently named workspace correctly. So it's fairly close, except on each "Rebuild container" I have to choose a workspace manually
    – Misiur
    May 14 at 10:13
  • It might not matter but can you document that portion of your problem.
    – Ramhound
    May 14 at 14:41


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.