Compile Radxa OS | Radxa Docs

[giscus[bot]]

Compile Radxa OS | Radxa Docs

This tutorial mainly introduces how to compile Radxa OS. Using the RadxaOS SDK (rsdk) source code we provide, combined with Dev Containers, makes compiling Radxa OS very convenient.

https://docs.radxa.com/en/cubie/a7a/low-level-dev/system-build/radxa-os

[IvanNekrasov88]

Hello, thying to build OS for cubie a7z with rsdk, but there is no /configs/product_soc_array.libjsonne. Maybe I did something wrong. Could you help me, please.

This is log:
vscode ➜ /workspaces/rsdk (main) $ rsdk
Building radxa-a733 bullseye kde...
RUNTIME ERROR: couldn't open import "../../../../configs/product_soc_array.libjsonnet": no match locally or in the Jsonnet library paths
/workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:3:27-84 thunk <product_soc_array> from <$>
/workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:85:18-35 thunk from <object >
/workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:85:5-53 object
/workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:(22:9)-(102:2) +:
/workspaces/rsdk/src/libexec/rsdk/../../share/rsdk/build/rootfs.jsonnet:(49:9)-(53:10) +:
Field "packages"
Field "mmdebstrap"
During manifestation

I`ve tryed to find out where is the problem, but I think that there is no such directory and file in repository:
vscode ➜ /workspaces/rsdk (main) $ git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: package-lock.json

no changes added to commit (use "git add" and/or "git commit -a")
vscode ➜ /workspaces/rsdk (main) $ ls src/share/rsdk/build/mod/packages
categories core.libjsonnet gnome.libjsonnet kde.libjsonnet xfce.libjsonnet
cli.libjsonnet gdm.libjsonnet i3.libjsonnet sway.libjsonnet
vscode ➜ /workspaces/rsdk (main) $ ls src/share/rsdk/build/mod/packages/configs
ls: cannot access 'src/share/rsdk/build/mod/packages/configs': No such file or directory
vscode ➜ /workspaces/rsdk (main) $ git diff package-lock.json | head
diff --git a/package-lock.json b/package-lock.json
index 3c060ba..fc41d83 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -12,7 +12,6 @@
"version": "0.72.0",
"resolved": "https://registry.npmjs.org/@devcontainers/cli/-/cli-0.72.0.tgz",
"integrity": "sha512-vDv33/I5POw1wDJmcMbOCTWd3xTk4bbVruJ9Qgr5eiLSl1OsfufN5WfeTZqgK1HeqrNqtH/xPyCKB2LXDNIv3w==",

•  "license": "MIT",
   "bin": {
  

vscode ➜ /workspaces/rsdk (main) $ git branch -a

• main
  remotes/origin/HEAD -> origin/main
  remotes/origin/main
  vscode ➜ /workspaces/rsdk (main) $ git ls-tree -r HEAD src/share/rsdk/build/mod/packages | grep configs
  vscode ➜ /workspaces/rsdk (main) $ git reset --hard HEAD
  HEAD is now at 5ac8ceb enable CONFIG_UPROBE_EVENTS and CONFIG_KPROBE_EVENTS
  vscode ➜ /workspaces/rsdk (main) $ git clean -fdx
  Removing .devcontainer/.devenv/bash-bash
  Removing .devcontainer/.devenv/bootstrap/
  Removing .devcontainer/.devenv/gc/
  Removing .devcontainer/.devenv/imports.txt
  Removing .devcontainer/.devenv/input-paths.txt
  Removing .devcontainer/.devenv/load-exports
  Removing .devcontainer/.devenv/nix-eval-cache.db
  Removing .devcontainer/.devenv/nixpkgs-config-c7c9559ef5bdea25.nix
  Removing .devcontainer/.devenv/profile
  Removing .devcontainer/.devenv/run
  Removing .devcontainer/.devenv/shell-022017c76520b192.sh
  Removing .devcontainer/.devenv/shell-8c19196cddacf19b.sh
  Removing .devcontainer/.devenv/shell-d42bd62f5a633878.sh
  Removing .devcontainer/.devenv/state/
  Removing .devcontainer/.devenv/task-names.txt
  Removing .devcontainer/.devenv/tasks.db
  Removing .devcontainer/.devenv/test-state/
  warning: failed to remove .devenv/: Device or resource busy
  Removing .devenv/.gitignore
  warning: failed to remove .direnv/: Device or resource busy
  Removing .direnv/.gitignore
  Removing .pre-commit-config.yaml
  Removing node_modules/
  Removing out/
  direnv: loading /workspaces/rsdk/.envrc
  direnv: using devenv
  ⠴ Configuring shell 4.5s

                                                                                     ↑↓ navd
  

✓ Configuring shell 10.4s
└ ✓ Evaluating shell 3056 files 5.4s
✓ Evaluating bash 1341 files 695ms
✓ Loading tasks 3.9s
└ ✓ Evaluating devenv.config.task.config 2530 files 3.9s
✓ Running tasks 140ms
└ ✓ devenv:enterShell 13ms
└ ✓ devenv:git-hooks:install 2 lines → prek installed at .git/hooks/pre-commit wit… 100ms
└ ✓ devenv:files 1 lines → Creating .pre-commit-config.yaml 19ms
└ ✓ devenv:files:cleanup 3ms
└ ✓ devenv:enterTest skipped 0ms
✨ devenv 2.0.4 is newer than devenv input (2.0.1) in devenv.lock. Run 'devenv update' to sync.

██████╗ ███████╗██████╗ ██╗ ██╗
██╔══██╗██╔════╝██╔══██╗██║ ██╔╝
██████╔╝███████╗██║ ██║█████╔╝
██╔══██╗╚════██║██║ ██║██╔═██╗
██║ ██║███████║██████╔╝██║ ██╗
╚═╝ ╚═╝╚══════╝╚═════╝ ╚═╝ ╚═╝
RadxaOS Software Development Kit

Please run rsdk shell to enter the full development shell.

direnv: export +AR +AS +CC +CONFIG_SHELL +CXX +DETERMINISTIC_BUILD +DEVENV_CMDLINE +DEVENV_DIRENVRC_ROLLING_UPGRADE +DEVENV_DIRENVRC_VERSION +DEVENV_DOTFILE +DEVENV_PROFILE +DEVENV_ROOT +DEVENV_RUNTIME +DEVENV_STATE +DEVENV_TASKS +DEVENV_TASK_FILE +HOST_PATH +IN_NIX_SHELL +LD +LOCALE_ARCHIVE +NIX_BINTOOLS +NIX_BINTOOLS_WRAPPER_TARGET_HOST_x86_64_unknown_linux_gnu +NIX_BUILD_CORES +NIX_CC +NIX_CC_WRAPPER_TARGET_HOST_x86_64_unknown_linux_gnu +NIX_CFLAGS_COMPILE +NIX_ENFORCE_NO_NATIVE +NIX_HARDENING_ENABLE +NIX_LDFLAGS +NIX_PKG_CONFIG_WRAPPER_TARGET_HOST_x86_64_unknown_linux_gnu +NIX_STORE +NM +OBJCOPY +OBJDUMP +PKG_CONFIG +PKG_CONFIG_PATH +PREK_HOME +PYTHONHASHSEED +PYTHONNOUSERSITE +PYTHONPATH +RANLIB +READELF +SIZE +SOURCE_DATE_EPOCH +STARSHIP_SESSION_KEY +STARSHIP_SHELL +STRINGS +STRIP +_PYTHON_HOST_PLATFORM +_PYTHON_SYSCONFIGDATA_NAME +__structuredAttrs +buildInputs +buildPhase +builder +cmakeFlags +configureFlags +depsBuildBuild +depsBuildBuildPropagated +depsBuildTarget +depsBuildTargetPropagated +depsHostHost +depsHostHostPropagated +depsTargetTarget +depsTargetTargetPropagated +doCheck +doInstallCheck +dontAddDisableDepTrack +hardeningDisable +mesonFlags +name +nativeBuildInputs +out +outputs +patches +phases +preferLocalBuild +propagatedBuildInputs +propagatedNativeBuildInputs +shell +shellHook +stdenv +strictDeps +system ~PATH ~XDG_DATA_DIRS
vscode ➜ /workspaces/rsdk (main) $ git submodule update --init --recursive
vscode ➜ /workspaces/rsdk (main) $ ls src/share/rsdk/build/mod/packages
categories core.libjsonnet gnome.libjsonnet kde.libjsonnet xfce.libjsonnet
cli.libjsonnet gdm.libjsonnet i3.libjsonnet sway.libjsonnet
vscode ➜ /workspaces/rsdk (main) $ ls src/share/rsdk/build/mod/packages/configs
ls: cannot access 'src/share/rsdk/build/mod/packages/configs': No such file or directory

[tangzz-radxa]

Thank you for the report. A few questions to help diagnose:

1. How did you obtain the rsdk source code? Did you use git clone --recurse-submodules https://github.com/RadxaOS-SDK/rsdk.git as shown in the documentation, or a different method?

2. Can you confirm whether git ls-tree -r HEAD -- src/share/rsdk/build/mod/packages/configs in the rsdk repository itself returns any results?

We are looking into this and will follow up with a more detailed answer shortly.

[RadxaYuntian]

It should be fixed when RadxaOS-SDK/rsdk#151 is merged.

[IvanNekrasov88]

Thank you for response!

1. Yes I used this comand and link git clone --recurse-submodules https://github.com/RadxaOS-SDK/rsdk.git as shown in the documentation.
   2./rsdk$ ls
   book.toml devenv.nix Makefile po
   debian devenv.yaml Makefile.custom README.md
   debs docs node_modules src
   devenv.local.nix.example externals package.json theme
   devenv.lock LICENSE package-lock.json
   ~/rsdk$ git ls-tree -r HEAD -- src/share/rsdk/build/mod/packages/configs
   no any results.

[tangzz-radxa]

The issue has been identified and resolved in our SDK. The product_soc_array.libjsonnet import path was corrected in commit 410e069. Please pull the latest rsdk and rebuild. If you encounter any further issues, feel free to let us know.

[IvanNekrasov88]

I did all as in instruction from the link. But had bad result. Ср, 18 марта 2026 г. в 18:30, giscus[bot] ***@***.***>:

…

Compile Radxa OS | Radxa Docs This tutorial mainly introduces how to compile Radxa OS. Using the RadxaOS SDK (rsdk) source code we provide, combined with Dev Containers, makes compiling Radxa OS very convenient. https://docs.radxa.com/en/cubie/a7a/low-level-dev/system-build/radxa-os — Reply to this email directly, view it on GitHub <#1487>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMYQC5IU72EL6LOK32SKV4D4RK6IDAVCNFSM6AAAAACWWTKIZKVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZGY4DIOJVGM> . You are receiving this because you commented.Message ID: ***@***.***>

[tangzz-radxa]

Thank you for reaching out! We apologize for the trouble you experienced.

To help you effectively, could you please share more details:

1. What board/product are you using?
2. What specific step failed? (e.g., Dev Container setup, SDK download, build command, etc.)
3. What error message or bad result did you get? (please paste any error output)
4. What OS/environment are you building from? (e.g., Ubuntu 22.04, macOS, etc.)

With more specifics we can pinpoint the issue quickly.

[IvanNekrasov88]

Hello!

1. I am using radxa cubie A7Z. And want to build OS by myself.
2. Faled after chosing platform radxa-a733 on rsdk TUI interface and then using official links.
   3.There is log:
   vscode ➜ /workspaces/rsdk (main) $ rsdk
   Building radxa-a733 bullseye kde...
   RUNTIME ERROR: couldn't open import "../../../../configs/product_soc_array.libjsonnet": no match locally or in the Jsonnet library paths
   /workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:3:27-84 thunk <product_soc_array> from <$>
   /workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:85:18-35 thunk from <object >
   /workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:85:5-53 object
   /workspaces/rsdk/src/share/rsdk/build/mod/packages/kde.libjsonnet:(22:9)-(102:2) +:
   /workspaces/rsdk/src/libexec/rsdk/../../share/rsdk/build/rootfs.jsonnet:(49:9)-(53:10) +:
   Field "packages"
   Field "mmdebstrap"
   During manifestation
3. Using Ubuntu 22 on vmWare workstation 17.

[IvanNekrasov88]

And one more error during command "rsdk shell"
vscode ➜ /workspaces/rsdk (main) $ rsdk shell
/workspaces/rsdk /workspaces/rsdk
✓ Configuring shell 44.1s
└ ✓ Downloading https://cache.nixos.org/nix-cache-info from cache.nixos.org 292ms
└ ✓ Downloading https://devenv.cachix.org/nix-cache-info from devenv.cachix.org 265ms
└ ✓ Updating inputs 6 files 5.8s
└ ✓ Downloading https://github.com/cachix/devenv/archive/4926e25455b8fdd90133914787ab52d948f7976c.tar.gz 2.5s
└ ✓ Downloading https://api.github.com/repos/cachix/git-hooks.nix/commits/HEAD from api.github.com 248ms
└ ✓ Downloading …/github.com/cachix/git-hooks.nix/ 560ms
└ ✓ Downloading https://api.github.com/repos/cachix/devenv-nixpkgs/commits/rolling from api.github.com 50ms
└ ✓ Downloading …github.com/cachix/devenv-nixpkgs/ 339ms
└ ✗ Evaluating shell 1576 files 1.5s
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/gi/git-buildpackage/
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/development/interpreters/python/mk-
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/gh/gh/package.nix'
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/build-support/go/module.nix'
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/gp/gptfdisk/package.nix'
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/jq/jq/package.nix'
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook/package.nix'
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook-admonish/
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook-cmdrun/package.nix'
│ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook-i18n-helpers/

[IvanNekrasov88]

INFO devenv_activity::builders: Configuring shell, devenv.ui.message: true, devenv.span_event_kind: 1, devenv.span_has_error: false, devenv.time_total: "1.98s"
at devenv-activity/src/builders.rs:490
in devenv_activity::builders::activity with activity_id: 9223372036854775809, devenv.user_message: "Configuring shell"

Error: x Evaluation error: Failed to get drvPath from shell derivation:
| … while calling the 'derivationStrict' builtin
| at «nix-internal»/derivation-internal.nix:37:12:
| 36|
| 37| strict = derivationStrict drvAttrs;
| | ^
| 38|
|
|
| … while evaluating derivation 'devenv-shell'
| whose name attribute is located at /nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/stdenv/generic/make-derivation.nix:536:13
|
| … while evaluating attribute 'DEVENV_PROFILE' of derivation 'devenv-shell'
|
| … while evaluating the option packages': | | … while evaluating definitions from ':
|
| (stack trace truncated; use '--show-trace' to show the full, detailed trace)
|
|
| error: 'mdbook-linkcheck' has been removed and replaced by 'mdbook-linkcheck2' due to incompatibility with mdbook version 0.5.0+

[IvanNekrasov88]

Thank you for your replies and fixing. But now I got the other error after build command in rsdk shell:
rsdk on  main [!] via  via ❄️ impure (devenv-shell-env) took 39s
⬢ [Docker] ❯ rsdk
Building radxa-a733 bullseye kde...
/nix/store/2hjsch59amjs3nbgh7ahcfzm2bfwl8zi-bash-5.3p9/bin/bash: line 1: bdebstrap: command not found

rsdk on  main [!] via  via ❄️ impure (devenv-shell-env) took 5s
⬢ [Docker] ❯

GIS status:
/rsdk$ git rev-parse HEAD
410e069

/rsdk$ git log -1 --oneline
410e069 (HEAD -> main, origin/main, origin/HEAD) fix(kde): correct relative path for product_soc_array import

[IvanNekrasov88]

Ive did it, but got this issue: /rsdk$ rsdk devcon up [1 ms] @devcontainers/cli 0.72.0. Node.js v24.14.0. linux 6.8.0-106-generic x64. (node:205127) [DEP0169] DeprecationWarning: url.parse()behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued forurl.parse()vulnerabilities. (Usenode --trace-deprecation ...` to show where the warning was created)
[1510 ms] Resolving Feature dependencies for 'ghcr.io/devcontainers/features/nix:1'...
[2874 ms] Soft-dependency 'ghcr.io/devcontainers/features/common-utils' is not required. Removing from installation order...
[3451 ms] Files to omit: ''
[3467 ms] Start: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-niv/container-features/0.72.0-1773912549887 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:bookworm --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -f /tmp/devcontainercli-niv/container-features/0.72.0-1773912549887/Dockerfile.extended -t vsc-rsdk-aeddc7140966c227d90df4ba5acb48f98c8b8502e3911be487740b3bdc20d5c0-features /tmp/devcontainercli-niv/empty-folder
[+] Building 1.4s (15/15) FINISHED docker:default
=> [internal] load build definition from Dockerfile.extended 0.0s
=> => transferring dockerfile: 3.50kB 0.0s
=> resolve image config for docker-image://docker.io/docker/dockerfile:1.4 1.0s
=> CACHED docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531bd80fb0a858632727cf7a112fbfd19b17e94c4e84ced81e24ef1a0dbc 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for mcr.microsoft.com/devcontainers/base:bookworm 0.3s
=> [context dev_containers_feature_content_source] load .dockerignore 0.0s
=> => transferring dev_containers_feature_content_source: 2B 0.0s
=> [context dev_containers_feature_content_source] load from client 0.0s
=> => transferring dev_containers_feature_content_source: 38.20kB 0.0s
=> [dev_containers_feature_content_normalize 1/3] FROM mcr.microsoft.com/devcontainers/base:bookworm@sha256:4d49e42a3eda8a8fd8437ecd8830d50a9 0.0s
=> CACHED [dev_containers_target_stage 2/5] RUN mkdir -p /tmp/dev-container-features 0.0s
=> CACHED [dev_containers_feature_content_normalize 2/3] COPY --from=dev_containers_feature_content_source devcontainer-features.builtin.env 0.0s
=> CACHED [dev_containers_feature_content_normalize 3/3] RUN chmod -R 0755 /tmp/build-features/ 0.0s
=> CACHED [dev_containers_target_stage 3/5] COPY --from=dev_containers_feature_content_normalize /tmp/build-features/ /tmp/dev-container-feat 0.0s
=> CACHED [dev_containers_target_stage 4/5] RUN echo "_CONTAINER_USER_HOME=$( (command -v getent >/dev/null 2>&1 && getent passwd 'root' || g 0.0s
=> CACHED [dev_containers_target_stage 5/5] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=nix_0,target=/tmp/build-f 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c4b0bef55ff5b3657d1d49a850e8ebafc2756abe98e9d55c43476232c6a7a39f 0.0s
=> => naming to docker.io/library/vsc-rsdk-aeddc7140966c227d90df4ba5acb48f98c8b8502e3911be487740b3bdc20d5c0-features 0.0s
[+] Building 0.0s (6/6) FINISHED docker:default
=> [internal] load build definition from updateUID.Dockerfile-0.72.0 0.0s
=> => transferring dockerfile: 1.52kB 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name (line 4) 0.0s
=> [internal] load metadata for docker.io/library/vsc-rsdk-aeddc7140966c227d90df4ba5acb48f98c8b8502e3911be487740b3bdc20d5c0-features:latest 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [1/2] FROM docker.io/library/vsc-rsdk-aeddc7140966c227d90df4ba5acb48f98c8b8502e3911be487740b3bdc20d5c0-features:latest 0.0s
=> CACHED [2/2] RUN eval $(sed -n "s/vscode:[^:]:([^:]):([^:]):[^:]:([^:])./OLD_UID=\1;OLD_GID=\2;HOME_FOLDER=\3/p" /etc/passwd); 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:8b2ffe814fed485e026dd4a0e2d3e4b77bb3206d94fb28871cfb5e44918c917b 0.0s
=> => naming to docker.io/library/vsc-rsdk-aeddc7140966c227d90df4ba5acb48f98c8b8502e3911be487740b3bdc20d5c0-features-uid 0.0s

1 warning found (use docker --debug to expand):

• InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name (line 4)
  [5170 ms] Start: Run: docker run --sig-proxy=false -a STDOUT -a STDERR --mount source=/home/niv/DSM_A7Z/rsdk/rsdk/..,target=/workspaces,type=bind,consistency=cached --mount type=volume,src=nix-store-0h84muu6o2ab1iiq1n7lomfofcl4knc612hedfuroumio7a2grhk,dst=/nix --mount type=bind,src=/home/niv/DSM_A7Z/rsdk/rsdk/.devcontainer/.devenv,dst=/workspaces/rsdk/.devenv --mount type=bind,src=/home/niv/DSM_A7Z/rsdk/rsdk/.devcontainer/.direnv,dst=/workspaces/rsdk/.direnv -l devcontainer.local_folder=/home/niv/DSM_A7Z/rsdk/rsdk -l devcontainer.config_file=/home/niv/DSM_A7Z/rsdk/rsdk/.devcontainer/devcontainer.json --ulimit nofile=1024:524288 --cap-add SYS_ADMIN --privileged -v /dev:/dev --entrypoint /bin/sh vsc-rsdk-aeddc7140966c227d90df4ba5acb48f98c8b8502e3911be487740b3bdc20d5c0-features-uid -c echo Container started
  Container started
  !!!In this step terminal frised!!! pres ctrl-c
  rsdk$ rsdk devcon
  vscode ➜ /workspaces/rsdk (main) $ export PATH="$PWD/src/bin:$PATH"
  vscode ➜ /workspaces/rsdk (main) $ rsdk shell
  /workspaces/rsdk /workspaces/rsdk
  ✓ Configuring shell 38.3s
  └ ✓ Downloading https://cache.nixos.org/nix-cache-info from cache.nixos.org 154ms
  └ ✓ Downloading https://devenv.cachix.org/nix-cache-info from devenv.cachix.org 269ms
  └ ✗ Evaluating shell 1576 files 660ms
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/gi/git-buildpackage/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/development/interpreters/python/mk-python-derivation.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/gh/gh/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/build-support/go/module.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/gp/gptfdisk/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/jq/jq/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook-admonish/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook-cmdrun/package.nix'
  │ evaluating file '/nix/store/s0bdxxy4gki016irflyqlxy5mzr96kin-source/pkgs/by-name/md/mdbook-i18n-helpers/package.nix'

This error looks like this: error: 'mdbook-linkcheck' has been removed and replaced by 'mdbook-linkcheck2' due to incompatibility with mdbook version 0.5.0+

I`ve remove all containers and rebuild it several minutes ago and show you the result.

[tangzz-radxa]

Thanks for the follow-up. We checked the current rsdk main branch, and this build path does require bdebstrap.

In the current source tree:

• src/libexec/rsdk/rsdk-build runs sudo bdebstrap ...
• src/libexec/rsdk/rsdk-setup installs bdebstrap
• .devcontainer/devcontainer.json runs src/bin/rsdk setup in postCreateCommand

So if you are inside the devcontainer and bdebstrap is still missing, the most likely cause is that the post-create setup step did not complete successfully.

Please run the setup step manually inside the rsdk repo, then reopen the shell and try again:

src/bin/rsdk setup
rsdk shell
rsdk

If src/bin/rsdk setup fails, please paste its full output here, because that output should show which dependency/setup step is being blocked.

[RadxaYuntian]

Please edit devenv.nix and change mdbook-linkcheck to mdbook-linkcheck2 before entering devcontainer.

Please also put your log in
```
xxx
```
block to have better readability.

[tangzz-radxa]

The bdebstrap command is missing because the post-create setup step did not complete successfully inside your devcontainer.

Root cause: In the current rsdk source tree, src/libexec/rsdk/rsdk-build runs sudo bdebstrap ..., and src/libexec/rsdk/rsdk-setup is responsible for installing it. The .devcontainer/devcontainer.json runs src/bin/rsdk setup as a postCreateCommand. If that setup step failed, bdebstrap will not be available.

Solution:

1. Edit devenv.nix in the rsdk root and change mdbook-linkcheck to mdbook-linkcheck2 before entering the devcontainer.
2. Rebuild your devcontainer: rsdk devcon up
3. Enter the container and run rsdk again.

If the issue persists, please check the devcontainer build log (run rsdk devcon up with verbose output) and confirm whether the postCreateCommand step completes without error. The log should show rsdk setup finishing successfully before the container is ready.

[IvanNekrasov88]

Great thanks! Now it works normaly and I built output.img for my cubie A7Z. Have a nice day!

[tgnews]

Hi,

does radxa plan to publish debian 13 trixie for the radxa Rock 4 series?
if yes: do you have an estimate when this will be published?
and will it be possible to upgrade from debain 12 to debain 13?

thanks
Thomas

[tangzz-radxa]

Hi Thomas,

Thank you for your interest in Debian 13 (Trixie) for the Rock 4 series.

We do not have a confirmed release schedule for Debian 13 Trixie on Rock 4 to share at this time. We recommend monitoring the official Rock 4 download page at https://docs.radxa.com/rock4 for the latest available images and release announcements.

Regarding upgrading from Debian 12 to Debian 13: we generally recommend a fresh installation rather than an in-place distribution upgrade, as the latter can introduce compatibility issues with board-specific packages and firmware.

For the most current availability and roadmap information, please reach out to our sales team at sales@radxa.com who can provide further guidance.

Thank you for your patience.

[tangzz-radxa]

Thank you for your interest in Debian 13 Trixie for Rock 4. We are evaluating the release but do not have a confirmed timeline yet. As Rock 4 is a mature platform, we recommend checking the official download page (docs.radxa.com/rock4) for the latest available images. In-place upgrades between major Debian versions are generally not tested or recommended — a fresh installation is the safest approach.