microsoft / vscode-remote-try-node

Node.js sample project for trying out Dev Containers
https://aka.ms/vscode-remote/containers/getting-started
MIT License
684 stars 683 forks source link

Problems trying to run using Podman with Windows 11 #60

Closed andreselim closed 1 year ago

andreselim commented 2 years ago

SO: Windows 11 Version 21H2 (OS Build 22000.739) podman.exe version 4.1.1 VSCode: Version: 1.68.1 (user setup) WSL Kernel version: 5.10.102.1

I got this error trying to run remote-development (vscode-remote-try-node) on Windows using podman Below the links I had use to set up: https://www.redhat.com/sysadmin/run-podman-windows https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers https://blog.lifeishao.com/2021/12/30/replacing-docker-with-podman-for-your-vscode-devcontainers/

And the error I got: [42 ms] Remote-Containers 0.238.2 in VS Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630). [41 ms] Start: Resolving Remote [45 ms] Start: Run: wsl -l -v [105 ms] Start: Run: wsl -d podman-machine-default -e /bin/sh -c echo ~ [227 ms] Start: Run: wsl -d podman-machine-default -e /bin/sh -c cd '/root' && /bin/sh [236 ms] Start: Run in host: id -un [297 ms] root [297 ms] [298 ms] Start: Run in host: cat /etc/passwd [300 ms] Start: Run in host: echo ~ [301 ms] /root [301 ms] [302 ms] Start: Run in host: test -x '/root/.vscode-remote-containers/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/node' [303 ms] [303 ms] [304 ms] Start: Run in host: test -f '/root/.vscode-remote-containers/dist/vscode-remote-containers-server-0.238.2.js' [305 ms] [305 ms] [310 ms] userEnvProbe: loginInteractiveShell (default) [310 ms] userEnvProbe shell: /bin/bash [2316 ms] Start: Run in Host: /bin/sh [2324 ms] Start: Run in container: for pid in cd /proc && ls -d [0-9]*; do { echo $pid ; readlink /proc/$pid/cwd ; readlink /proc/$pid/ns/mnt ; cat /proc/$pid/stat | tr " [4368 ms] userEnvProbe is taking longer than 2 seconds. Process not found. [10326 ms] userEnvProbe is taking longer than 10 seconds. Avoid waiting for user input in your shell's startup scripts. Continuing. [10347 ms] Start: Check Docker is running [10347 ms] Start: Run in Host: podman version --format {{.Server.APIVersion}} [10560 ms] Server API version: 4.1.1 [10565 ms] Start: Run in Host: podman volume ls -q [10729 ms] Start: Run in Host: podman volume create --label vsch.local.repository=https://github.com/Microsoft/vscode-remote-try-node --label vsch.local.repository.unique=true vscode-remote-try-node-6789fd329eb29bc56aab44eb27506206 [11077 ms] Start: Run in Host: tar --no-same-owner -x -f - [11185 ms] Start: Run in Host: podman build -f /tmp/vsch/bootstrap-image/0.238.2/bootstrap.Dockerfile -t vsc-volume-bootstrap /tmp/vsch/bootstrap-image/0.238.2 STEP 1/4: FROM mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14 Trying to pull mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14... Getting image source signatures Copying blob 93dce5d3774d done
Copying blob 8663204ce13b done
Copying blob 79f0fdc0e058 done
Copying config f4fb89e582 done
Writing manifest to image destination Storing signatures STEP 2/4: RUN apk add --no-cache nodejs npm make g++ docker-cli docker-compose ; error running container: error from /usr/bin/crun creating container for [/bin/sh -c apk add --no-cache nodejs npm make g++ docker-cli docker-compose ;]: creating cgroup directory /sys/fs/cgroup/systemd/buildah-buildah650293479: No such file or directory : exit status 1 ERRO[0008] did not get container create message from subprocess: EOF Error: error building at STEP "RUN apk add --no-cache nodejs npm make g++ docker-cli docker-compose ;": error while running runtime: exit status 1 [19404 ms] Command failed: podman build -f /tmp/vsch/bootstrap-image/0.238.2/bootstrap.Dockerfile -t vsc-volume-bootstrap /tmp/vsch/bootstrap-image/0.238.2 [19405 ms] Exit code 1

Any thoughts! Thanks in advance

Chuxel commented 1 year ago

Please raise issues about the extension at https://github.com/microsoft/vscode-remote-relase. Thanks!