Content

Technology stack: Conty, bubblewrap, and user namespaces.

---

Filesystem and persistence

The container image is read-only by default. At runtime, OverlayFS is used to enable a read-write layer.

All changes are stored in the following directory:

$HOME/.local/share/MoonBot/overlayfs

The MoonBot working directory inside the container is located at:

$HOME/.local/share/MoonBot/overlayfs/opt/MoonBot

For convenience, a symbolic link is created in the user’s home directory:

$HOME/.config/MoonBot → $HOME/.local/share/MoonBot/overlayfs/opt/MoonBot

Running the container does not affect system-wide Wine settings or the host OS configuration.

---

Alternative launch without the container

If an up-to-date version of Wine is already installed on the system (version 9.x minimum, version 10.0 or higher recommended), MoonBot can be launched directly.

For optimal performance, support for vkd3d and all related dependencies is also recommended.

MoonBot can be started with the following command:

wine MoonBot.exe

---

System configuration

On some distributions (for example, Ubuntu), unprivileged user namespaces may be disabled.

If required, they can be enabled manually using the following command:

sudo sysctl kernel.unprivileged_userns_clone=1

For Ubuntu 24.04 and newer, an additional setting is required:

sudo sysctl kernel.apparmor_restrict_unprivileged_userns=0

---

Command-line options

The MoonBot container supports the following startup options:

-h — display help information

-r — reset the container while preserving the MoonBot working directory and settings

-R — same as -r, but also attempts to restore overwritten MoonBot binaries (recommended after a failed update)

-RESETFULL — destructive mode, performs a full reset of the container, removing all data and settings

To display the help text, run:

./MoonBot -h

---

MoonBot for Linux

A container image packaged into a single executable file, designed to run MoonBot on Linux using Wine.

Download