vyos-documentation.git/docs, branch build-vyos-fixes

docs: build-vyos: document build.py kernel build wrapper

2026-11-07T06:38:37+00:00

build-kernel.sh only builds the kernel. The build.py wrapper in scripts/package-build/linux-kernel installs the build dependencies, fetches and verifies the kernel source, builds the kernel and all firmware and out-of-tree modules defined in package.toml. - Document build.py usage and its --packages and --install-dependencies options. - Update paths from packages/linux-kernel to scripts/package-build/linux-kernel and from data/defaults.json to data/defaults.toml; drop references to the removed Jenkinsfile. - Update the out-of-tree module list to match package.toml. - Drop the per-module build instructions which referenced renamed or removed helper scripts, and the no longer existing ADD_FW_FILES.

docs: build-vyos: update kernel version examples to 6.18.60

2026-11-07T06:38:37+00:00

docs: build-vyos: add macOS notes for Docker builds

2026-11-07T06:38:37+00:00

On macOS a Docker volume must be used instead of a bind mount from the user's home. Also warn about case-insensitive macOS file systems which break Linux kernel source checkouts.

docs: build-vyos: refer to official Docker install guide

2026-11-07T06:38:37+00:00

The inlined Docker installation steps go stale with every Docker release. Link to the upstream Debian installation guide instead.

docs: build-vyos: clone vyos-build before it is used

2026-11-07T06:38:37+00:00

The prerequisites assumed an existing vyos-build checkout, but the repository was only cloned in the "Build ISO" section, and the native build section showed build commands under a "clone" heading. - Add a "Get the Source Code" step at the start of the prerequisites and drop the duplicate clones from "Build from source" and "Build ISO". - List Docker before the native build, as it is the recommended way. - Native build now refers to the "Build ISO" commands. - Rename the ISO "Packages" subsection to "Custom Packages" and move the build_custom_packages label to it, as referenced from "Install". - Group "ISO Build Issues" and the APT verbosity patch under "Troubleshooting". - Minor fixes: MyST inline code, list lead-in, kernel checkout path, stale VyOS 1.3 comment.

docs: Update Firewall bridge page to VyOS 1.5 standards (#2364)

2026-11-03T18:18:25+00:00

* docs: Update Firewall bridge page to VyOS 1.5 standards * Apply wording and formatting suggestions from code review Co-authored-by: Daniil Baturin --------- Co-authored-by: Daniil Baturin

Merge pull request #2361 from vyos/T9496-secure-boot-add-image

2026-11-02T18:21:38+00:00

secure-boot: T9496: document Secure Boot signature check on "add system image"

Merge pull request #2329 from jeleel-muibi/docs-azure-nic-ip-forwarding

2026-11-02T17:41:24+00:00

docs: document Azure forwarding prerequisites

T3871: bind interface names to hardware slots instead of hw-id (#2246)

2026-10-31T10:53:23+00:00

* docs: T3871: describe how interface names are assigned Names are no longer derived from the hw-id node. They are bound to the slot the hardware occupies and recorded in a mapping file, so document what decides a name, what happens when a card is replaced or added, and how to rename an interface. The troubleshooting page said to pin a MAC with hw-id when interfaces were renamed after a VM migration or a clone. That node no longer exists and the situation it describes no longer arises, so replace it with a pointer to the new section and a note on where to look when an interface really is missing. * docs: T3871: drop hw-id from the example output The node is gone from the CLI, so example configuration dumps which still show it no longer match what a reader sees on their own system. Remove it from the shown output only; no prose changes. The comparison shown on the testing page is rewritten rather than trimmed, as deleting the lines would have left an edit level behind with nothing under it.

secure-boot: T9496: document Secure Boot signature check on "add system image"

2026-10-28T21:02:56+00:00

With Secure Boot enabled, "add system image" now aborts if the Linux Kernel of the new image is not signed by an enrolled Machine Owner Key, since that image would not boot. Describe the check, its error message and when it is skipped, and point to it from the image update page.