Repository files navigation

TheLinuxServer.io team brings you another container release featuring:

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more!
• Discord - realtime support / chat with the community and the team.
• Discourse - post on our community forum.
• GitHub - view the source for all of our repositories.
• Open Collective - please consider helping us by either donating or contributing to our budget

RPCS3 is a multi-platform open-source Sony PlayStation 3 emulator and debugger written in C++ for Windows, Linux, macOS and FreeBSD.

We utilise the docker manifest for multi-platform awareness. More information is available from dockerhere and our announcementhere.

Simply pullinglscr.io/linuxserver/rpcs3:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

The application can be accessed at:

• https://yourhost:3001/

This image uses a self-signed certificate by default. This naturally means the scheme ishttps.If you are using a reverse proxy which validates certificates, you need todisable this check for the container.

Modern GUI desktop apps may have compatibility issues with the latest Docker syscall restrictions. You can use Docker with the--security-opt seccomp=unconfined setting to allow these syscalls on hosts with older Kernels or libseccomp versions.

HTTPS is required for full functionality. Modern browser features such as WebCodecs, used for video and audio, will not function over an insecure HTTP connection.

By default, this container has no authentication. The optionalCUSTOM_USER andPASSWORD environment variables enable basic HTTP auth, which is suitable only for securing the container on a trusted local network. For internet exposure, we strongly recommend placing the container behind a reverse proxy, such asSWAG, with a robust authentication mechanism.

The web interface includes a terminal with passwordlesssudo access. Any user with access to the GUI can gain root control within the container, install arbitrary software, and probe your local network.

While not generally recommended, certain legacy environments specifically those with older hardware or outdated Linux distributions may require the deactivation of the standard seccomp profile to get containerized desktop software to run. This can be achieved by utilizing the--security-opt seccomp=unconfined parameter. It is critical to use this option only when absolutely necessary as it disables a key security layer of Docker, elevating the potential for container escape vulnerabilities.

This container is based onDocker Baseimage Selkies, which provides the following environment variables and run configurations to customize its functionality.

WATERMARK_LOCATION Options:

• 1: Top Left
• 2: Top Right
• 3: Bottom Left
• 4: Bottom Right
• 5: Centered
• 6: Animated

To launch the desktop session in a different language, set theLC_ALL environment variable. For example:

• -e LC_ALL=zh_CN.UTF-8 - Chinese
• -e LC_ALL=ja_JP.UTF-8 - Japanese
• -e LC_ALL=ko_KR.UTF-8 - Korean
• -e LC_ALL=ar_AE.UTF-8 - Arabic
• -e LC_ALL=ru_RU.UTF-8 - Russian
• -e LC_ALL=es_MX.UTF-8 - Spanish (Latin America)
• -e LC_ALL=de_DE.UTF-8 - German
• -e LC_ALL=fr_FR.UTF-8 - French
• -e LC_ALL=nl_NL.UTF-8 - Netherlands
• -e LC_ALL=it_IT.UTF-8 - Italian

For accelerated apps or games, render devices can be mounted into the container and leveraged by applications using:

--device /dev/dri:/dev/dri

This feature only supportsOpen Source GPU drivers:

TheDRINODE environment variable can be used to point to a specific GPU.

DRI3 will work on aarch64 given the correct drivers are installed inside the container for your chipset.

Note: Nvidia support is not available for Alpine-based images.

Nvidia GPU support is available by leveraging Zink for OpenGL. When a compatible Nvidia GPU is passed through, it will also beautomatically utilized for hardware-accelerated video stream encoding (using thex264enc full-frame profile), significantly reducing CPU load.

Enable Nvidia support with the following runtime flags:

For Docker Compose, you must first configure the Nvidia runtime as the default on the host:

sudo nvidia-ctk runtime configure --runtime=docker --set-as-defaultsudo systemctl restart docker

Then, assign the GPU to the service in yourcompose.yaml:

services:  rpcs3:    image: lscr.io/linuxserver/rpcs3:latest    deploy:      resources:        reservations:          devices:            - driver: nvidia              count: 1              capabilities: [compute,video,graphics,utility]

There are two methods for installing applications inside the container: PRoot Apps (recommended for persistence) and Native Apps.

Natively installed packages (e.g., viaapt-get install) will not persist if the container is recreated. To retain applications and their settings across container updates, we recommend usingproot-apps. These are portable applications installed to the user's persistent$HOME directory.

To install an application, use the command line inside the container:

proot-apps install filezilla

A list of supported applications is availablehere.

You can install packages from the system's native repository using theuniversal-package-install mod. This method will increase the container's start time and is not persistent. Add the following to yourcompose.yaml:

environment:    -DOCKER_MODS=linuxserver/mods:universal-package-install    -INSTALL_PACKAGES=libfuse2|git|gdb

These variables can be used to lock down the desktop environment for single-application use cases or to restrict user capabilities.

These variables act as presets, enabling multiple hardening options at once. Individual options can still be set to override the preset.

Using environment variables every facet of the application can be configured.

Boolean settings accepttrue orfalse. You can also prevent the user from changing a boolean setting in the UI by appending|locked. The UI toggle for this setting will be hidden.

• Example: To force CPU encoding on and prevent the user from disabling it:

  -e SELKIES_USE_CPU="true|locked"

These settings accept a comma-separated list of values. Their behavior depends on the number of items provided:

• Multiple Values: The first item in the list becomes the default selection, and all items in the list become the available options in the UI dropdown.

• Single Value: The provided value becomes the default, and the UI dropdown is hidden because the choice is locked.

• Example: Force the encoder to bejpeg with no other options available to the user:

  -e SELKIES_ENCODER="jpeg"

Range settings define a minimum and maximum for a value (e.g., framerate).

• To set a range: Use a hyphen-separatedmin-max format. The UI will show a slider.

• To set a fixed value: Provide a single number. This will lock the value and hide the UI slider.

• Example: Lock the framerate to exactly 60 FPS.

  -e SELKIES_FRAMERATE="60"

The server can be forced to use a single, fixed resolution for all connecting clients. This mode is automatically activated ifSELKIES_MANUAL_WIDTH,SELKIES_MANUAL_HEIGHT, orSELKIES_IS_MANUAL_RESOLUTION_MODE is set.

• IfSELKIES_MANUAL_WIDTH and/orSELKIES_MANUAL_HEIGHT are set, the resolution is locked to those values.
• IfSELKIES_IS_MANUAL_RESOLUTION_MODE is set totrue without specifying width or height, the resolution defaults to1024x768.
• When this mode is active, the client UI for changing resolution is disabled.

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---services:rpcs3:image:lscr.io/linuxserver/rpcs3:latestcontainer_name:rpcs3environment:      -PUID=1000      -PGID=1000      -TZ=Etc/UTCvolumes:      -/path/to/config:/configports:      -3000:3000      -3001:3001shm_size:"1gb"restart:unless-stopped

docker run -d \  --name=rpcs3 \  -e PUID=1000 \  -e PGID=1000 \  -e TZ=Etc/UTC \  -p 3000:3000 \  -p 3001:3001 \  -v /path/to/config:/config \  --shm-size="1gb" \  --restart unless-stopped \  lscr.io/linuxserver/rpcs3:latest

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate<external>:<internal> respectively. For example,-p 8080:80 would expose port80 from inside the container to be accessible from the host's IP on port8080 outside the container.

You can set any environment variable from a file by using a special prependFILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variableMYVAR based on the contents of the/run/secrets/mysecretvariable file.

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional-e UMASK=022 setting.Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read uphere before asking for support.

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the userPUID and groupPGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instancePUID=1000 andPGID=1000, to find yours useid your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

We publish variousDocker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

• Shell access whilst the container is running:

  dockerexec -it rpcs3 /bin/bash

• To monitor the logs of the container in realtime:

  docker logs -f rpcs3

• Container version number:

  docker inspect -f'{{ index .Config.Labels "build_version" }}' rpcs3

• Image version number:

  docker inspect -f'{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/rpcs3:latest

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult theApplication Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

• Update images:

  • All images:

    docker-compose pull

  • Single image:

    docker-compose pull rpcs3

• Update containers:

  • All containers:

    docker-compose up -d

  • Single container:

    docker-compose up -d rpcs3

• You can also remove the old dangling images:

  docker image prune

• Update the image:

  docker pull lscr.io/linuxserver/rpcs3:latest

• Stop the running container:

  docker stop rpcs3

• Delete the container:

  docker rm rpcs3

• Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your/config folder and settings will be preserved)

• You can also remove the old dangling images:

  docker image prune

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-rpcs3.gitcd docker-rpcs3docker build \  --no-cache \  --pull \  -t lscr.io/linuxserver/rpcs3:latest.

The ARM variants can be built on x86_64 hardware and vice versa usinglscr.io/linuxserver/qemu-static

docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with-f Dockerfile.aarch64.

• 22.09.25: - Rebase to Debian Trixie.
• 19.06.25: - Initial release.