shawly / docker-ps3netsrv

Alpine based docker image for ps3netsrv (with arm compatibility). Built with the latest ps3netsrv binaries from aldostools (built from sources)
GNU General Public License v3.0
92 stars 13 forks source link

[HELP] #18

Closed binarymelon closed 3 years ago

binarymelon commented 3 years ago

I have read and followed all troubleshooting steps from the README.md?

SSBoYXZlIHJlYWQsIGZvbGxvd2VkIGFuZCB0cmllZCBldmVyeSB0cm91Ymxlc2hvb3Rpbmcgc3RlcCwgYnV0IGl0IHN0aWxsIGRvZXNuJ3Qgd29yaywgcGxlYXNlIGhlbHAgbWUu

System configuration:
Please execute every command here and post the output. I will not answer tickets where these outputs are missing.

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.14
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        5eb3275
 Built:             Tue Dec  1 19:14:24 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.14
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       5eb3275
  Built:            Tue Dec  1 19:21:08 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.3.9
  GitCommit:        ea765aba0d05254012b0b9e595e995c09186427f
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker ps -a -f "ancestor=shawly/ps3netsrv":

CONTAINER ID        IMAGE                     COMMAND             CREATED             STATUS              PORTS                      NAMES
eeafd56016c1        shawly/ps3netsrv:unraid   "/init"             10 minutes ago      Up 10 minutes       0.0.0.0:38008->38008/tcp   PS3NetSrv

Output of docker logs CONTAINERNAME (replace CONTAINERNAME with your ps3netsrv container's name):

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-adduser: executing...

-------------------------------------
GID/UID
-------------------------------------

User uid:    99
User gid:    100
-------------------------------------

[cont-init.d] 00-adduser: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2021-03-31 20:10:46.573365985  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:25.127403178  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:31.910943131  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:32.913419963  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:33.913599785  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:34.911707411  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:35.916569228  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:36.917607311  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:43.016734018  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:44.017940333  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:45.210499391  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:46.847070720  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:47.850590039  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:53.107744129  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:11:54.110792833  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:12:01.901835577  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:12:08.338339946  ps3netsrv build 20201030 (mod by aldostools)
2021-03-31 20:12:18.345727398  ps3netsrv build 20201030 (mod by aldostools)

Output of id (you should be logged in with the user that owns your games directory):

uid=99(nobody) gid=100(users) groups=100(users),98(nobody)

Output of docker exec --user ps3netsrv CONTAINERNAME id (replace CONTAINERNAME with your ps3netsrv container's name):

uid=99(ps3netsrv) gid=100(users) groups=100(users)

Output of ls -l /path/to/your/games/folder:

total 0
drwxr-xr-x 1 nobody users 10 Mar 31 15:25 GAMES/
drwxr-xr-x 1 nobody users 81 Mar 31 15:27 PS2ISO/
drwxr-xr-x 1 nobody users 10 Mar 31 15:25 PS3ISO/

Output of docker exec CONTAINERNAME ls -l /games (replace CONTAINERNAME with your ps3netsrv container's name):

total 0
drwxr-xr-x 1 ps3netsrv users 10 Mar 31 15:25 GAMES
drwxr-xr-x 1 ps3netsrv users 81 Mar 31 15:27 PS2ISO
drwxr-xr-x 1 ps3netsrv users 10 Mar 31 15:25 PS3ISO

My docker run command or my docker-compose.yml:

I'm running on unraid, so I'm not entirely sure.
binarymelon commented 3 years ago

I'm not able to see any files or folders in multiman. Interestingly enough I can create directories, but not see them. I'm currently on the unraid tag (as a troubleshooting step) but was having the same behaviour on latest as well.

shawly commented 3 years ago

This is an UnRAID related issue, see here https://github.com/aldostools/webMAN-MOD/issues/333 there is no fix for this except for the workarounds described at the end of the issue thread, either the UnRAID devs have to fix this or aldos needs to implement a fix in ps3netsrv for this.

The unraid tag was just a test for the possible code fix from aldos but that didn't work and the change is also in the main branch already so the latest tag is the preferred one to use.