lucernae / devcontainer-nix Goto Github PK

Will capture the screenshots when it happens again.

Following the instruction for creating the .devcontainer using the CLI tool. I encound the following error when I try to open my project directory in the devcontainer.

[31584 ms] Command in container failed: '/path/to/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/helpers/check-requirements.sh'
[31584 ms] /path/to/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/helpers/check-requirements.sh: line 45: getconf: command not found
[31584 ms] Exit code 127
[31654 ms]
[31654 ms]

It seems that the getconf command is not available inside the container.

Environment

• Operating System:

Darwin MacBook.local 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:33:31 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8112 arm64

• Docker Version:

Client:
Cloud integration: v1.0.35+desktop.13
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:14:46 2024
OS/Arch: darwin/arm64
Context: desktop-linux

Server: Docker Desktop 4.29.0 (145265)
Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:18:02 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dorny/paths-filter action to v3

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/checkout digest to 0ad4b8f
• chore(deps): update nixpkgs to nixos-23.11
• chore(deps): update actions/cache action to v4
• chore(deps): update cachix/install-nix-action action to v26
• chore(deps): update docker/build-push-action action to v5
• chore(deps): update docker/login-action action to v3
• chore(deps): update docker/metadata-action action to v5
• chore(deps): update docker/setup-buildx-action action to v3
• chore(deps): update docker/setup-qemu-action action to v3
• chore(deps): lock file maintenance
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Error shown when running the Dockerfile build (either using buildx or build)

docker buildx build --platform linux/arm64/v8 .

error: unable to load seccomp BPF program: Invalid argument

Home-manager derivation doesn't work.
The flake based build says that it won't execute get-hm-version due to sus permissions.

Writing in this issue so I won't forget.

Diagnose:

• check store permission
  • all user can write, should be not possible
• check umask
  • already 022, should be okay
• reset permission and rebuild switch
  • weirdly set to 0757 again. should be 755
• check where it builds
  • in /tmp, so perhaps mount options is forcing the default file to be 757

will try solution on adding hooks to docker entrypoint to make sure /tmp uses the correct umask 022

It's a headache in Apple Silicon because docker downloaded x86_64 image and caused nix recipe inside to break because it is not compatible with host arch.

Proposed plan:

1. Use gh action from docker official (that can use multiarch build push on a single manifests list, not multiple tags)
2. Make a base nix Dockerfile that installs nix in the appropriate docker arch convention
3. Uses nix recipe to build the rest (like current method), to be compatible with devcontainer

Initial guess: the image was built using github action, thus sudo is built without proper permissions

It seems that specifying multiple devcontainer config is now supported as a subfolder. So we can just fill in examples in this repo directly. Looking forward to do that 🤣

I observed more and more features template, including nix in github codespace. However at the moment it's not that useful. We could try making the setup as another example and then overlay the same composition to support existing use case:

• default.nix
• nix direnv
• flake
• dockertools
• non-codespace devcontainer