-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscode+devcontainers w/Macos arm64 not working #29
Comments
Suggested in #29 Signed-off-by: ZHANG Yuntian <[email protected]>
This should be your real cause. Might want to check your file permissions and UID stuff. |
@RadxaYuntian yes, that's indeed it. I added "remoteUser": "root" to devcontainer.json and that got me further, but not all the way, see below. Looks like nix package libguestfs-appliance-1.46.0 isn't available aarch64. I'm currently looking into workarounds, not successful yet. • Trusting devenv.cachix.org on first use with the public key devenv.cachix.org-1:w1cLUi8dv3hnoSPGAuibQv+f9TZLr6cv/Hm9XgU50cw=
✖ Command produced the following output: ✔ Building shell in 9.1s. You might be rate limited by GitHub. |
Can you run |
root ➜ /workspaces/rsdk (main) $ devenv update ✖ Command produced the following output: Error: × Command |
We don't use |
I tried this as well, the result was same for |
I have updated the lock file and I now have 1.50 for libguestfs:
TBH I don't know how you can install binfmt support on MacOS with devcontainer. I know docker runs in VM on MacOS but I'm not sure how you are going to modify the base Linux system there. You might want to create a VM explicitly and follow this guide. |
Is this actually a rate limiting issue?
I've tried several ways, but it simply won't complete the building of rsdk and breaks with same message, consistently.
Aside (for zsh or other non-bash users, it may be useful to document that they should set:
"terminal.integrated.defaultProfile.linux": "bash",
In devcontainers.json. The rsdk script uses bash specific commands like shopt)
Using colima instead of docker desktop to run the daemon fairs worse, so I'm continuing with docker desktop.
I've cleaned out all docker builds, caches, etc and started fresh. This consistently happened. Is this a github rate limiting issue or another problem? I tried with a GITHUB PAT and the result is the same.
Here is the error message, and then trying again with a PAT. (all tokens/keys have been redacted):
direnv: loading /workspaces/rsdk/.envrc
direnv: loading https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc (sha256-XXXX)
direnv: using devenv
direnv: .envrc changed, reloading
error:
… while fetching the input 'git+file:///workspaces/rsdk'
✖ Command produced the following output:
Error: × Command
/nix/store/as63rjja0x63d1kw7d8xagb9s7glvwkl-nix-devenv-2.21.0pre20240412_b24a931/bin/nix --show-trace --extra-experimental- │ features nix-command --extra-experimental-features flakes --option warn-dirty false --keep-going --max-jobs 6 --option eval-cache false │ print-dev-env --profile /workspaces/rsdk/.devenv/gc/shell
failed with with exit code 1direnv: loading the environment failed
direnv: error exit status 1
vscode ➜ /workspaces/rsdk $ mkdir -p ~/.config/nix/ && echo 'access-tokens = github.com=XXXXXX' >> ~/.config/ni
x/nix.conf && src/bin/rsdk setup
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy main restricted
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy universe
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy-updates universe
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy multiverse
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse
deb [arch-=arm64,riscv64] http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
deb [arch-=arm64,riscv64] http://security.ubuntu.com/ubuntu/ jammy-security main restricted
deb [arch-=arm64,riscv64] http://security.ubuntu.com/ubuntu/ jammy-security universe
deb [arch-=arm64,riscv64] http://security.ubuntu.com/ubuntu/ jammy-security multiverse
deb [arch=arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports/ jammy main restricted universe multiverse
deb [arch=arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports/ jammy-updates main restricted universe multiverse
deb [arch=arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports/ jammy-backports main restricted universe multiverse
deb [arch=arm64,riscv64] http://ports.ubuntu.com/ubuntu-ports/ jammy-security main restricted universe multiverse
Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:5 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
Hit:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:7 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
Hit:8 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
bash-completion is already the newest version (1:2.11-5ubuntu1).
binfmt-support is already the newest version (2.2.1-2).
libfakeroot is already the newest version (1.28-1ubuntu1).
libfakeroot:riscv64 is already the newest version (1.28-1ubuntu1).
bdebstrap is already the newest version (0.4.0-1).
debian-archive-keyring is already the newest version (2021.1.1ubuntu2).
debian-ports-archive-keyring is already the newest version (2022.02.15).
libfakechroot is already the newest version (2.20.1+ds-2).
libfakechroot:riscv64 is already the newest version (2.20.1+ds-2).
qemu-user-static is already the newest version (1:6.2+dfsg-2ubuntu6.21).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Name: cachix
Store paths: /nix/store/l5bymdl1wy7m6ih5p0fziczdrg3jfxvg-cachix-1.7.4-bin
Locked flake URL: github:cachix/devenv/6e318854efa95c5e67a1152547f838754e8f0306?narHash=sha256-XXXX
Configured https://devenv.cachix.org binary cache in /home/vscode/.config/nix/nix.conf
warning: 'flake:devenv#packages.aarch64-linux.default' is already installed
• Building shell ...
error:
… while fetching the input 'git+file:///workspaces/rsdk'
✖ Command produced the following output:
✔ Building shell in 0.1s.
Error: × Command
/nix/store/as63rjja0x63d1kw7d8xagb9s7glvwkl-nix-devenv-2.21.0pre20240412_b24a931/bin/nix --show-trace --extra-experimental- │ features nix-command --extra-experimental-features flakes --option warn-dirty false --keep-going --max-jobs 6 --option eval-cache false │ print-dev-env --profile /workspaces/rsdk/.devenv/gc/shell
failed with with exit code 1You might be rate limited by GitHub.
Please request a PAT from GitHub website, and add it to your Dev Container:
mkdir -p ~/.config/nix/ && echo 'access-tokens = github.com=YOUR_GITHUB_PAT' >> ~/.config/nix/nix.conf && src/bin/rsdk setup
You can run above command in a new terminal once you complete this one.
Press Enter to continue...
direnv: loading /workspaces/rsdk/.envrc
direnv: loading https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc (sha256-XXXX)
direnv: using devenv
direnv: .envrc changed, reloading
error:
… while fetching the input 'git+file:///workspaces/rsdk'
✖ Command produced the following output:
Error: × Command
/nix/store/as63rjja0x63d1kw7d8xagb9s7glvwkl-nix-devenv-2.21.0pre20240412_b24a931/bin/nix --show-trace --extra-experimental- │ features nix-command --extra-experimental-features flakes --option warn-dirty false --keep-going --max-jobs 6 --option eval-cache false │ print-dev-env --profile /workspaces/rsdk/.devenv/gc/shell
failed with with exit code 1direnv: loading the environment failed
direnv: error exit status 1
vscode ➜ /workspaces/rsdk $
The text was updated successfully, but these errors were encountered: