This is a Docker container for ps3netsrv (or ps3netsvr).
ps3netsrv for WebMAN-MOD by aldostools. Binaries built from the latest sources.
The architectures supported by this image are:
| Architecture | Tag | Status |
|---|---|---|
| x86-64 | amd64-latest | working |
| arm64 | arm64v8-latest | experimental |
| armhf | arm32v6-latest | experimental |
Lo and behold this is the first ps3netsrv container with experimental arm32 and arm64 support!
I'm declaring the arm images as experimental because I only own an older first generation RaspberryPi Model B+ I can't properly test the image on other devices, technically it should work on all RaspberryPi models and similar SoCs. While emulating the architecture with qemu works and can be used for testing, I can't guarantee that there will be no issues, just try it.
I would be glad if you could create a small report (choose ARM Compatibility Report) to tell me which device you've tested and if it's working or not.
NOTE: The Docker command provided in this quick start is given as an example and parameters should be adjusted to your need.
Launch the ps3netsrv docker container with the following command:
docker run -d \
--name=ps3netsrv \
-p 38008:38008 \
-v $HOME:/games:rw \
shawly/ps3netsrv
Where:
$HOME: This location contains files from your host that need to be accessible by the application.
docker run [-d] \
--name=ps3netsrv \
[-e <VARIABLE_NAME>=<VALUE>]... \
[-v <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS]]... \
[-p <HOST_PORT>:<CONTAINER_PORT>]... \
shawly/ps3netsrv
| Parameter | Description |
|---|---|
| -d | Run the container in background. If not set, the container runs in foreground. |
| -e | Pass an environment variable to the container. See the Environment Variables section for more details. |
| -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the Data Volumes section for more details. |
| -p | Set a network port mapping (exposes an internal container port to the host). See the Ports section for more details. |
To customize some properties of the container, the following environment
variables can be passed via the -e parameter (one for each variable). Value
of this parameter has the format <VARIABLE_NAME>=<VALUE>.
| Variable | Description | Default |
|---|---|---|
USER_ID |
ID of the user the application runs as. See User/Group IDs to better understand when this should be set. | 1000 |
GROUP_ID |
ID of the group the application runs as. See User/Group IDs to better understand when this should be set. | 1000 |
TZ |
[TimeZone] of the container. Timezone can also be set by mapping /etc/localtime between the host and the container. |
Etc/UTC |
The following table describes data volumes used by the container. The mappings
are set via the -v parameter. Each mapping is specified with the following
format: <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS].
| Container path | Permissions | Description |
|---|---|---|
/games |
rw | This is the path ps3netsrv will serve to clients. |
Here is the list of ports used by the container. They can be mapped to the host
via the -p parameter (one per port mapping). Each mapping is defined in the
following format: <HOST_PORT>:<CONTAINER_PORT>. The port number inside the
container cannot be changed, but you are free to use any port on the host side.
| Port | Mapping to host | Description |
|---|---|---|
| 38008 | Mandatory | Port used for ps3netsrv. |
As seen, environment variables, volume mappings and port mappings are specified while creating the container.
The following steps describe the method used to add, remove or update parameter(s) of an existing container. The generic idea is to destroy and re-create the container:
- Stop the container (if it is running):
docker stop ps3netsrv
- Remove the container:
docker rm ps3netsrv
- Create/start the container using the
docker runcommand, by adjusting parameters as needed.
Example compose file included - 'ps3netsrv-compose.yml'
Make sure to adjust according to your needs. Note that only mandatory network ports are part of the example. Uncomment out the network_mode if you wish to use the docker host instead of bridge mode.
A cifs example is added incase you want to access a large shared drive.
version: '2.2'
services:
ps3netsrv:
build:
context: '.'
container_name: ps3netsrv
image: *Changeme*
environment:
- TZ=Europe/London
- USER_ID=1001
- GROUP_ID=1001
#network_mode: "host"
ports:
- "38008:38008"
volumes:
- "ps3data:/games:rw"
restart: on-failure:5
cpus: 4.0
mem_limit: 1073741824
volumes:
ps3data:
driver: local
driver_opts:
type: cifs
o: username=ps3,password=ps3,uid=1001,gid=1001
device: "//*Changeme*/Shared/PS3"
If the system on which the container runs doesn't provide a way to easily update the Docker image, the following steps can be followed:
- Fetch the latest image:
docker pull shawly/ps3netsrv
- Stop the container:
docker stop ps3netsrv
- Remove the container:
docker rm ps3netsrv
- Start the container using the
docker runcommand.
When using data volumes (-v flags), permissions issues can occur between the
host and the container. For example, the user within the container may not
exists on the host. This could prevent the host from properly accessing files
and folders on the shared volume.
To avoid any problem, you can specify the user the application should run as.
This is done by passing the user ID and group ID to the container via the
USER_ID and GROUP_ID environment variables.
To find the right IDs to use, issue the following command on the host, with the user owning the data volume on the host:
id <username>
Which gives an output like this one:
uid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)
The value of uid (user ID) and gid (group ID) are the ones that you should
be given the container.
Having troubles with the container or have questions? Please create a new issue.