Incus for ChromiumOS . .

OpenOS-Project-Creat · February 16, 2025, 2:56pm

There is this Project, which its sole mission is to make ChromiumOS as Generic in terms of hardware support as the Android Generic Project. [ https://android-generic.github.io/ ]

This ChromiumOS Project goes by the name of Brunch, its goals is to is to replace all Proprietary Google Features with Open Source Alternatives ontop of a ChromiumOS RootC that Official Google Signed Recovery Images gets rebuild/merged into a Custom ChromiumOS Build, with overlays + bins + ebuilds + portage-scripts within the recoveries.

The current Brunch-toolchain uses LXC to replace both the Proprietary Android+Linux Subsystems in OEM ChromeOS [ Proprietary Builds/Compilations of ChromiumOS ].

Though LXC is now back in the hands of Canonical, I am hoping the Incus Community can assist with Brunch’s goals

github.com/sebanc/brunch-toolchain

toolchain_chroot

main

#!/bin/bash
export HOME=/home/chronos
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
export LD_LIBRARY_PATH=/usr/local/lib64:/usr/local/lib:/usr/lib64:/usr/lib:/lib64:/lib
export C_INCLUDE_PATH=/usr/local/include/ncurses
export GCONV_PATH=/usr/local/lib64/gconv
export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
export PYTHON=/usr/local/bin/python3
export PYTHONHOME=/usr/local
export PERL5LIB=/usr/local/lib/perl5/5.32.0
export XML_CATALOG_FILES="/usr/local/etc/xml/catalog"
export SGML_CATALOG_FILES="/usr/local/etc/sgml/catalog"
export LANGUAGE=en_US.UTF-8
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8

# libc location fix
for f in /usr/local/lib64/*_nonshared.a; do
file=$(echo "$f" | sed 's#/usr/local/lib64/##g')
if [ ! -e "/usr/lib64/$file" ]; then sudo ln -s -v "/usr/local/lib64/$file" "/usr/lib64/$file"; fi

This file has been truncated. show original

github.com/sebanc/brunch-toolchain

create_toolchain.sh

main

#!/bin/bash

BUILDPATH=$(dirname $(realpath "$0"))

build_all=1

mkdir -p ./bootstrap/usr/local

if [ ! -z $build_all ] || [ ! -z $build_gcc ]; then

mkdir -p ./gcc/out
curl -L https://ftp.gnu.org/gnu/gcc/gcc-10.2.0/gcc-10.2.0.tar.gz -o ./gcc.tar.gz
tar zxf ./gcc.tar.gz -C ./gcc --strip 1
rm ./gcc.tar.gz
cd ./gcc
./contrib/download_prerequisites
cd ./out
../configure --prefix=/usr/local --libdir=/usr/local/lib64 --enable-languages=c,c++ --with-glibc-version=2.27 --disable-multilib --disable-nls --disable-libssp --disable-host-shared
make -j$(($(nproc)-1))
make DESTDIR="$BUILDPATH"/bootstrap install-strip

This file has been truncated. show original

github.com/sebanc/brunch-toolchain

BUILDING.md

main

# Building the toolchain

The toolchain build script has only been tested under Ubuntu 20.04.

### Requirements

- root access.
- I am not sure about the exact dependencies yet, they should be quite limited (mostly build-essentials, gawk and curl) but I still have to verify that.

## Getting the source

Clone the main branch and enter the source directory:

```
git clone -b main https://github.com/sebanc/brunch-toolchain.git brunch-toolchain
cd brunch-toolchain
```

## Building the toolchain.

This file has been truncated. show original

OpenOS-Project-Creat · February 16, 2025, 3:38pm

In regards to Brunch,

The best path to go, is to have a Generic ChromiumOS Base Image that Brunch can use that is accessible to everyone.

We could merge OpenFyde + ThoriumOS together . . .

https://openfyde.io/

ThoriumOS maintainer Alex313031 has already begun merging both OpenFyde & WayneOS overlays, patches, binaries, ebuilds into his ChromiumOS Builds.

So we should conrinue down this path.

In regards . . . Thorium: The Fastest Open Source Chromium-based Browser?

In this Linux AVX2 is a holding repo with repo urls for all architectures that Thorium Browser itself is compiled against.

Alex313031 usually updates the browsers first before the OSes.

So once all browsers are on the latest stable of 132 he will then update the ThoriumOS Builds in all the architectures he compiles against.

hereisjames · February 17, 2025, 9:07am

LXC is not “back in the hands of Canonical,” it never was with them and it stays here as an open source project.

If you mean LXD, then it was always in Canonical’s hands and remains there, the only change being a more restrictive licence especially as it relates to contributions. In that case Incus is the more openly licensed alternative to LXD, and after more than a year apart there’s now some notable differences between the two in terms of features.

OpenOS-Project-Creat · February 17, 2025, 10:12am

Isn’t LXC the legacy version of LXD?

Isnt LXD the modern version of LXC?

Why was Incus Created if LXC is still open-source? Couldn’t LXC be maintained & had features added as ot was fone for Incus?

Unless LXC is too close in naming conventions to LXD to even be associated with being open-source & was the reason a new container project with a new name was invented?

Also have you taken a look at this?

So I guess LXC was tainted by Canonical as Stéphane Graber has mentioned . . .

stgraber · February 17, 2025, 6:45pm

No, it’s not.
LXC and liblxc is a low level container manager written in C.
It’s still used as the container runtime by LXD, Incus and others.

Incus uses liblxc/LXC, same as LXD did.
Incus is a community fork of LXD.

LXC existed long before LXD and still exists today, it’s used by both LXD and Incus as the low level container runtime alongside LXCFS for the resource overlay.

As you linked, the biggest bit of confusion comes from LXD using lxc as its command line command, which itself has nothing to do with LXC.

In any case, LXD is gone, it’s just a Canonical project now and we don’t have any control on what’s happening over there. On our side, we have LXC, LXCFS and Incus so things are must nicer and clearer now.

hereisjames · February 18, 2025, 6:28pm

Nicer, indeed.

I thought we should get to a common understanding on taxonomy and functionality here so that the requestor can be clearer with their ask.

OpenOS-Project-Creat · February 21, 2025, 2:04am

Doing some more research these 2 projects streamline & create an easy to use TUI & GUI hybrid utilities/tools that automates the Brunch Framework/Toolchain.

These could be piped through Distrobuilder somehow . . . ?

OpenOS-Project-Creat · March 4, 2025, 9:25pm

This could be used for a template for Incus specifically . . .

Simply swap out the LXC bits for Incus bits . . .

github.com/chromebrew/chromebrew

New package: LXC

master ← supechicken:lxc

opened 06:49PM - 23 Jul 24 UTC

supechicken

+75 -42

> [!NOTE] > This package will not work on ChromeOS stock kernel, user need to r…ebuild their kernel with `SECURITY_CHROMIUMOS=n` to use it (see https://github.com/containers/crun/issues/1121 for more info) ### Run the following to get this pull request's changes locally for testing. ```bash CREW_REPO=https://github.com/supechicken/chromebrew.git CREW_BRANCH=lxc crew update ```

OpenOS-Project-Creat · March 9, 2025, 7:09pm

https://wiki.gentoo.org/wiki/Incus/Gentoo_Github_pullrequest_testing