[Bug]: vscode devcontainers "features" feature fails on Windows and MacOS

[JustinGrote]

Issue Description

Dev containers features fails on the podman buildx command, it looks like the temp file doesn't get copied correctly by the builder.

Steps to reproduce the issue

Steps to reproduce the issue

1. Create a devcontainer with a feature - https://code.visualstudio.com/blogs/2022/09/15/dev-container-features
2. Open the devcontainer in local vscode

Simple Example:

// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/dotnet
{
  "name": "PowerShell Binary Module",
  // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
  "image": "mcr.microsoft.com/devcontainers/dotnet:0-7.0",
  "features": {
     "ghcr.io/devcontainers/features/powershell:1": {
       "version": "latest"
     }
  },
  "containerUser": "vscode"
}

Describe the results you received

[4484 ms] Start: Run: podman buildx build --load --build-context dev_containers_feature_content_source=C:\Users\jgrote\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1675271780761 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/dotnet:0-7.0 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-yourfirstpsmoduleincsharp-a2b143a26a2888997d906577ede0f015-features -f C:\Users\jgrote\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1675271780761\Dockerfile.extended c:\Users\jgrote\AppData\Roaming\Code - Insiders\User\globalStorage\ms-vscode-remote.remote-containers\data\empty-folder
time="2023-02-01T09:16:22-08:00" level=error msg="While reading directory C:\\Us
ers\\jgrote\\AppData\\Roaming\\Code - Insiders\\User\\globalStorage\\ms-vscode-r
emote.remote-containers\\data\\empty-folder: EOF"
Error: stat /var/tmp/libpod_builder4232675966/build/C:/Users/jgrote/AppData/Loca
l/Temp/devcontainercli/container-features/0.25.2-1675271780761/Dockerfile.extend
ed: no such file or directory

[5085 ms] Error: Command failed: podman buildx build --load --build-context dev_containers_feature_content_source=C:\Users\jgrote\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1675271780761 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/dotnet:0-7.0 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-yourfirstpsmoduleincsharp-a2b143a26a2888997d906577ede0f015-features -f C:\Users\jgrote\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1675271780761\Dockerfile.extended c:\Users\jgrote\AppData\Roaming\Code - Insiders\User\globalStorage\ms-vscode-remote.remote-containers\data\empty-folder
[5086 ms]     at Aoe (c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1893:1355)
[5086 ms]     at uT (c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1893:1291)
[5086 ms]     at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[5086 ms]     at async Poe (c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1899:2128)
[5086 ms]     at async Zf (c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:1899:3278)
[5086 ms]     at async aue (c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:2020:15276)
[5087 ms]     at async oue (c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js:2020:15030)
[5097 ms] Exit code 1
[5101 ms] Command failed: C:\Users\jgrote\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe --ms-enable-electron-run-as-node c:\Users\jgrote\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.266.1\dist\spec-node\devContainersSpecCLI.js up --user-data-folder c:\Users\jgrote\AppData\Roaming\Code - Insiders\User\globalStorage\ms-vscode-remote.remote-containers\data --docker-path podman --docker-compose-path podman-compose --workspace-folder c:\Users\jgrote\Projects\YourFirstPSModuleInCSharp --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\Users\jgrote\Projects\YourFirstPSModuleInCSharp --log-level debug --log-format json --config c:\Users\jgrote\Projects\YourFirstPSModuleInCSharp\.devcontainer\devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true

Describe the results you expected

Describe the results you expected

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[vrothberg]

Thanks for reaching out, @JustinGrote!

@flouthoc PTAL

[3belut]

I have the same issue, also probably the same as microsoft/vscode-remote-release#7408.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[mikegoatly]

See also here: microsoft/vscode-remote-release#8103

I'm running into this as well using the latest version of podman on Windows (currently 4.4.1). It looks to me that the absolute path not being forwarded correctly to podman. For example, in the OP the following is being passed to podman:

-f C:\Users\jgrote\AppData\Local\Temp\devcontainercli\container-features\0.25.2-1675271780761\Dockerfile.extended

But the path that's being reported as not found in podman is:

/var/tmp/libpod_builder4232675966/build/C:/Users/jgrote/AppData/Local/Temp/devcontainercli/container-features/0.25.2-1675271780761/Dockerfile.extended

I would have thought it should be mapped to:

/mnt/c/Users/jgrote/AppData/Local/Temp/devcontainercli/container-features/0.25.2-1675271780761/Dockerfile.extended

[G3N7]

Same thing happening in 4.4.4

[Jacques-Peeters]

Same thing happening in 4.4.2 and 4.4.4 on Mac M1.

Managed to make it work by uninstalling, manually installing 4.3.1 .

[acidghost]

This is happening on 4.5.0 too, on macOS M1. Even with a fresh VM.

[dmorand17]

I'm experiencing the same behavior on 4.5.0 on M1 Mac

[ReeSilva]

The same on Windows and Podman 4.5.0