vanilla-os / core-image Goto Github PK

View Code? Open in Web Editor NEW

17.0 3.0 5.0 262 KB

Containerfile for the Vanilla OS Core image.

Home Page: https://images.vanillaos.org/#/recipe/vanilla-os-core-image

License: GNU General Public License v3.0

Shell 100.00%

containers hacktoberfest images oci-images vanillaos

core-image's Introduction

Vanilla OS Core Image

Containerfile for building a Vanilla OS Core image.

Important

This image is not intended to be used directly. It is used as a base image for other images. Like the Vanilla OS Desktop image, etc.

Build

Note

The fsguard compiled plugin .so file should be downloaded from the latest release and be placed under a plugins directory beside the recipe.yml file.

vib build recipe.yml
podman image build -t vanillaos/core .

Verify Image Build Provenance Attestation

All the image builds/pushes are attested for build provenance and integrity using the attest-build-provenance` action. The attestations can be verified here or by having the latest version of GitHub CLI installed in your system. Then, execute the following command:

gh attestation verify oci://ghcr.io/vanilla-os/core:main --owner Vanilla-OS

core-image's People

Contributors

Stargazers

Watchers

Forkers

matbme axtloss msgpo kbdharun taukakao

core-image's Issues

Move `/includes.container/usr/share/abroot` to desktop-image

The file currently contains configuration which is desktop-image specific and as such should be moved to that repository.

Compatibility with rpm-ostree?

Feature Description

Make Fedora Silverblue compatible with VanillaOS 2 and allow rebasing from one to another.

Rationale

Both use ghcr OCI images (from Orchid on), and on Fedora Atomic, you can freely rebase from Silverblue (Gnome) to Kinoite (KDE) to uBlue (custom spins) to Bazzite (gaming-distro).

Additional Information

Maybe I'm super dumb and have no clue how different both are.
I like the concept of VOS a lot, and maybe, Fedora Atomic and VOS are cross-compatible due to their immutable nature.

Use `overlay` storage in podman by default

It's required to create a file /etc/containers/storage.conf with content

[storage]
driver = "overlay"

to ensure the user uses overlay - instead of vfs - as driver for podman

Bug: `apx.json` config file is missing in apx module

/tmp becomes readonly when running out of space during operation

When running an operation that would take up too much space in the root partition it will make /tmp readonly which causes a plethora of problems.

A better solution would be to limit the space that an operation can take up.

(fu) Upload Containerfile as an artifact when building from a PR

Builds always result in layers with different digests

Docker not being aware of the older version of the image, makes it rebuild the entire recipe from scratch, this results in the user being forced to re-pull the whole image during an update.

~~The solution is to pull the older version before building the new one, this populates the store with the old layers, making docker use them instead of build everything from scratch.~~

The actual solution is to share a cache across builds.

firmware: failed to load rtl_bt/rtl8723b_config.bin (-2)

When turning on from suspend, I always see new messages about failing to load rtl_bt/rtl8723b_config. Reading the kernel logs, I found the following segment to repeat all the time:

Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
Bluetooth: hci0: RTL: rom_version status=0 version=1
Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin
Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin
bluetooth hci0: firmware: failed to load rtl_bt/rtl8723b_config.bin (-2)
bluetooth hci0: firmware: failed to load rtl_bt/rtl8723b_config.bin (-2)
bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
Bluetooth: hci0: RTL: cfg_sz -2, total sz 22496
PM: suspend exit
rfkill: input handler disabled
Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
r8169 0000:02:00.0 enp2s0: Link is Down
Bluetooth: hci0: RTL: fw version 0x0e2f9f73
Bluetooth: MGMT ver 1.22
Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control rx/tx
input: LIFT Mouse as /devices/virtual/misc/uhid/0005:046D:B031.000A/input/input31
hid-generic 0005:046D:B031.000A: input,hidraw1: BLUETOOTH HID v0.10 Mouse [LIFT] on 74:df:bf:0f:62:68
r8169 0000:02:00.0 enp2s0: Link is Down
rfkill: input handler enabled
PM: suspend entry (deep)
Filesystems sync: 0.037 seconds
(NULL device *): firmware: direct-loading firmware i915/skl_dmc_ver1_27.bin
(NULL device *): firmware: direct-loading firmware rtlwifi/rtl8723befw_36.bin
(NULL device *): firmware: direct-loading firmware regulatory.db
(NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Bluetooth: hci0: unexpected event for opcode 0x0c24

Notes:
The hid-generic 0005:046D:B031.000A identifier increments the last section (.000A) with each repetition.
The number in filesystems sync: 0.037 seconds always slightly differs.

Configure zram to use sensible values for swap

Feature Description

Currently zram uses the default (256M) value for swap space. We need to change that in the config file.

Rationale

Ideally, it should allow up to half the RAM for swap.

Additional Information

No response

bug: VSO shell upon reboot gives OCI runtime error and prompts for reset

Current behaviour

When I open the Console after rebooting, the setup process fails with the following error:

Config loaded from /etc/vso/config.json
Starting container...                   	 [ OK ]
Installing basic packages...            	 [ OK ]
Setting up devpts mounts...             	 [ OK ]
Setting up read-only mounts...          	 [ OK ]
Setting up read-write mounts...         	 [ OK ]
Setting up host's sockets integration...	 [ OK ]
Integrating host's themes, icons, fonts...	 [ OK ]
Setting up distrobox profile...         	 [ OK ]
Setting up sudo...                      	 [ OK ]
Setting up groups...                    	 [ OK ]
Setting up users...                     	 [ OK ]
Setting up skel...                      	 [ OK ]
Setting up init system...               	 [ OK ]
Firing up init system...                	 [ OK ]

Container Setup Complete!
Error: OCI runtime error: crun: unlockpt: Invalid argument
 WARNING  It is impossible to reach the VSO shell. Do you want to reset it? (This will remove all your software installed in the subsystem) [y/N]

Expected behaviour

VSO shell must initialize correctly (without runtime errors) and shouldn't prompt again for reset.

Software Details

Vanilla OS Orchid Build 102 (Fresh Install, done yesterday)
Test environment: Proxmox VE

vanilla-os / core-image Goto Github PK

core-image's Introduction

Vanilla OS Core Image

Build

Verify Image Build Provenance Attestation

core-image's People

Contributors

Stargazers

Watchers

Forkers

core-image's Issues

Feature Description

Rationale

Additional Information

Feature Description

Rationale

Additional Information

Current behaviour

Expected behaviour

Software Details

Recommend Projects

Recommend Topics

Recommend Org