vanilla-os/vso-image

Containerfile for the Vanilla OS VSO image.

Vanilla OS VSO Image

Containerfile for building a Vanilla OS VSO image.

This image is based on top of vanillaos/pico and adds the systemd package to obtain a full systemd environment for VSO.

Build

podman image build -t vanillaos/vso .

vso-image's Issues

Install vanilla tools in vso

Stuff like cur-gpu and nrun are useful in VSO and does not require to be executed by host

Install nano by default

Feature Description

The text editor nano should be installed by default inside the container so the user doesn't have to install it themself.

Rationale

Many programs and most users require an editor and nano is an easy to use editor that is very widespread.

Additional Information

No response

Host-exported abroot commands does not work in VSO

This is probably due to the fact that ABRoot requires privileges.

Include "passthrough" binaries for `shutdown` and `reboot`

Feature Description

Include "passthrough" binaries for shutdown and reboot

Rationale

These commands don't work from inside the vso-shell, but are expected to.

Additional Information

No response

Unable to unlock the apt

The unlock command gives this error in Orchid

Unlocking /usr/bin/private.apt
Error: rename /usr/bin/private.apt /usr/bin/apt: read-only file system

Export script failing when installing with apt

Issue Description

When trying to install nano you get:

trying to export nano
E: Problem executing scripts DPkg::Post-Invoke '/usr/share/vso/hooks/apt-post'
E: Sub-process returned an error code

Steps to Reproduce

• vso shell
• sudo apt install nano

On what version of Vanilla OS this happens?

Unreleased

Additional Information

No response

Handle desktop entries exports on `apt install`/`apt remove`

Since vso will become the default shell, we have to handle exports from the inside, this way if the user install a package using apt install, any desktop entry related to that package will be exported to the host system.

To achieve this, we can simply wrap the apt command to check if the active shell is vso and call vso export/vso unexport commands after each apt install/apt remove.

host-shell bad substitution

Issue Description

When running the host-shell command without arguments, it just returns:
/usr/bin/host-shell: line 16: ${$host_shell:-/bin/bash}: bad substitution

Steps to Reproduce

• enter a new container with a recent version of this image
• run host-shell

On what version of Vanilla OS this happens?

Unreleased

Additional Information

Probably caused by 5c83432

Wrap distrobox-host-exec to setup the right environment

Dbox does more stuff than host-spawn, mainly:

XDG_RUNTIME_DIR="/run/host/${XDG_RUNTIME_DIR}"
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/host/$(echo "${DBUS_SESSION_BUS_ADDRESS}" | cut -d '=' -f2-)"

this makes host-spawn work on initful containers.

Ref: https://github.com/89luca89/distrobox/blob/3435f4d27070a99668bfa29a3e508db4ecc09009/distrobox-host-exec#L186C3-L186C51

Incorrect rendering of German umlauts in vso shell

These should be identical:

This should say Öffentlich:

"Authorization required, but no authorization protocol specified" after installing something

Issue Description

This is because of the apt post hook https://github.com/Vanilla-OS/vso-image/blob/main/includes.container/usr/share/vso/hooks/apt-post

The system seems to be trying to create a new dbus instance which kills the old one. Not sure about the details here yet.

The user has to reboot to start graphical programs again.

Steps to Reproduce

• run sudo su -c 'XDG_RUNTIME_DIR=/run/user/$UID; DBUS_SESSION_BUS_ADDRESS='unix:path=/run/user/$UID/bus'; host-shell ls' $SUDO_USER
• run any graphical app like gedit

On what version of Vanilla OS this happens?

Unreleased

Rebase on top of vso-sysd once ready

ref Vanilla-OS/pico-image#9

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

No man page for apt

Issue Description

The apt command in the VSO container does not have a man page installed by default. Since it is recommended to use apt instead of the vso program inside the container, users will look for apt documentation, and not find it.

Steps to Reproduce

• Start the VSO container
• Run man apt - the output is No manual entry for apt

On what version of Vanilla OS this happens?

Unreleased

Additional Information

I was able to fix this in my machine by running sudo apt reinstall apt from inside the container.