containers/osu

Simon Bruder 3ed6442b49

Update 3rd party rulesets

Some did not build and were removed. This change also makes building
much faster, as the build now caches NuGet packages and uses one stage
per ruleset, so they can be built in parallel (by passing `--jobs N`).

2024-05-09 02:34:30 +02:00

1,004 B

Raw Blame History

osu!lazer in docker

How to use

Building

Using podman/buildah:

buildah build --format docker --layers -t osu --build-arg OSU_VERSION=2024.412.1 --jobs 0

Change 2024.412.1 to the newest osu! version. By changing --jobs 0 to a positive integer N, at most N build stages will be run in parallel.

Running

Place run.sh in a directory of your choice. On first run, the directories data and import will be created.

To import a beatmap, place it in the import directory, open a graphical file manager and drag-and-drop the file into osu!.

Known Bugs

osu! shows Couldn’t list input devices. Is libasound2-dev installed? at startup. Fixing this requires installing libasound2-dev in the runtime container and mounting /dev/snd in the container. This is not done as this container is intended to be used with PulseAudio (which works).

This is not an official product by ppy Pty Ltd. osu! is a registered trademark by ppy Pty Ltd.