메뉴
Use this skill when launching Resonite in the container, setting up the host for the first time, or stopping/inspecting the running container. Covers the init.sh → run.sh flow, host prerequisites (X11, GPU, audio, user namespaces), and the named-volume persistence model.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use this skill when Resonite fails to launch, crashes on startup, freezes, shows a black/blank window, or has no audio in the container. Maps the common failure modes to their root causes (X11, GPU, shared memory, audio, user namespaces, drive-letter resolution) and the setting that fixes each.
Use this skill when performing GitHub operations for this repo such as creating pull requests, writing commit messages, or managing issues. Covers branch/PR conventions and the commit style used here.
Use this skill when the user communicates in Japanese or requests Japanese-language output. Ensures natural, technically accurate Japanese for comments, commit messages, and conversation in this repository.
SOC 직업 분류 기준
| name | run-resonite |
| description | Use this skill when launching Resonite in the container, setting up the host for the first time, or stopping/inspecting the running container. Covers the init.sh → run.sh flow, host prerequisites (X11, GPU, audio, user namespaces), and the named-volume persistence model. |
This skill guides launching and operating the containerized Resonite.
DISPLAY + /tmp/.X11-unix/X* socket exist). init.sh finds the user-owned X socket and generates a hostname-independent auth cookie — no native-Wayland setup is needed or attempted.nvidia-container-toolkit./run/user/<uid>/pulse/native — without it Resonite's engine hangs at the audio onboarding step.kernel.apparmor_restrict_unprivileged_userns=0 on the host (Ubuntu 24.04+ defaults it on, which blocks Steam Linux Runtime's pressure-vessel):
sudo sysctl kernel.apparmor_restrict_unprivileged_userns=0 # temporary
echo 'kernel.apparmor_restrict_unprivileged_userns=0' | sudo tee /etc/sysctl.d/99-resonite-userns.conf && sudo sysctl --system # persistent
./init.sh # probe host → write .env (UID/GID, DISPLAY, XAUTHORITY_HOST, GPU UUID, render/video GIDs, RESONITE_DIR) + generate .xauth
./run.sh # detect GPU → docker compose up --build with the right overlay
If Resonite is not at the default Steam path:
RESONITE_DIR=/path/to/Resonite ./init.sh
init.sh prints non-fatal warnings if the audio socket or the userns sysctl are missing — resolve those before expecting a clean launch.
run.sh forwards extra args to docker compose with the overlay already selected:
./run.sh logs -f # follow logs
./run.sh up -d # detached
./run.sh down # stop and remove
First launch is slow: it downloads Proton/Steam Linux Runtime and rsyncs ~2 GB of Resonite into the resonite-app volume. Subsequent launches sync only changed files.
Four named volumes survive down (everything else regenerates per container): resonite-app (install copy), resonite-share (Proton/runtime + login & settings), resonite-cache (asset/shader cache), resonite-prefix (Wine prefix). To fully reset, remove them with ./run.sh down -v — note this forces a full re-sync and re-login.