docker-emulatorjs icon indicating copy to clipboard operation
docker-emulatorjs copied to clipboard

[BUG] Error downloading default config files

Open andres125correa opened this issue 1 year ago • 6 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Current Behavior

I just installed using docker , followed the default guide and trying to retrieve the default files, it gets stuck at downloading /data/gb/corners/default.png

This means that I do not see any emulator on the main side. I don't know why. I used to be able to set it up on docker easily. I have all my paths correct. The permissions on the folders are wide open. I am pulling the latest one build. Maybe there is a problem on the site it pulls the configuration files. It is unusable . Am I the only one having this issue on the most recent build ?

Expected Behavior

When first installed , it should just be able to download all configuration files ( the default fileset) , and after scanning roms , be able to see it on the main page.

Steps To Reproduce

have docker compose file with the default configuration. Enter the site, download default/dl files , gets stuck

Environment

- OS: Ubuntu 23.10
- How docker service was installed: distro's package manager

CPU architecture

x86-64

Docker creation

docker compose file 

version: "2.1"

services:

  emulatorjs:

    image: lscr.io/linuxserver/emulatorjs:latest

    container_name: emulatorjs

    environment:

      - PUID=1000

      - PGID=1000

      - TZ=UTC-6

      #- SUBFOLDER=/ #optional

    volumes:

      - /home/<user>/Emulatorjs:/config

      - /home/<user>/Retroarch_games/NES:/data/nes/roms

      - /home/<user>/Retroarch_games/SNES_games:/data/snes/roms

      - /home/<user>/Retroarch_games/N64_games:/data/n64/roms

      - /home/<user>/Retroarch_games/GBC:/data/gbc/roms

      - /home/<user>/Retroarch_games/GBA_games:/data/gba/roms

      - /home/<user>/Retroarch_games/nintendo_ds_games:/data/nds/roms

      - /home/<user>/Retroarch_games/PS1:/data/psx/roms

      

    ports:

      - 3001:3000

      - 7080:80

      - 4001:4001 #optional

    restart: unless-stopped

Container logs

[migrations] started

[migrations] no migrations found

───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗

      ██║     ██╔════╝██║██╔═══██╗

      ██║     ███████╗██║██║   ██║

      ██║     ╚════██║██║██║   ██║

      ███████╗███████║██║╚██████╔╝

      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io

───────────────────────────────────────

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID:    1000

User GID:    1000

───────────────────────────────────────

generating ED25519 keypair...done

peer identity: 12D3KooWBnkAA6BArPpkvZ7VXrZue2QxtF2eXJfRCohkaoWeYM84

initializing IPFS node at /data/.ipfs

[custom-init] No custom files found, skipping...

Connection to localhost (127.0.0.1) 80 port [tcp/http] succeeded!

Initializing daemon...

Kubo version: 0.24.0

Repo version: 15

System version: amd64/linux

Golang version: go1.21.3

2024/02/18 02:37:22 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.

Swarm listening on /ip4/127.0.0.1/tcp/4001

Swarm listening on /ip4/127.0.0.1/udp/4001/quic-v1

Swarm listening on /ip4/127.0.0.1/udp/4001/quic-v1/webtransport/certhash/uEiAAp-ODgPfpKxlNjFQcsI43HD1LRoRY5ULwgDYCVoFK0w/certhash/uEiCJdPZ3OUjyS9v9MX7zAodgVoNSMf3tuybGwJgCa0cjdQ

Swarm listening on /ip4/172.19.0.2/tcp/4001

Swarm listening on /ip4/172.19.0.2/udp/4001/quic-v1

Swarm listening on /ip4/172.19.0.2/udp/4001/quic-v1/webtransport/certhash/uEiAAp-ODgPfpKxlNjFQcsI43HD1LRoRY5ULwgDYCVoFK0w/certhash/uEiCJdPZ3OUjyS9v9MX7zAodgVoNSMf3tuybGwJgCa0cjdQ

Swarm listening on /p2p-circuit

Swarm announcing /ip4/127.0.0.1/tcp/4001

Swarm announcing /ip4/127.0.0.1/udp/4001/quic-v1

Swarm announcing /ip4/127.0.0.1/udp/4001/quic-v1/webtransport/certhash/uEiAAp-ODgPfpKxlNjFQcsI43HD1LRoRY5ULwgDYCVoFK0w/certhash/uEiCJdPZ3OUjyS9v9MX7zAodgVoNSMf3tuybGwJgCa0cjdQ

Swarm announcing /ip4/172.19.0.2/tcp/4001

Swarm announcing /ip4/172.19.0.2/udp/4001/quic-v1

Swarm announcing /ip4/172.19.0.2/udp/4001/quic-v1/webtransport/certhash/uEiAAp-ODgPfpKxlNjFQcsI43HD1LRoRY5ULwgDYCVoFK0w/certhash/uEiCJdPZ3OUjyS9v9MX7zAodgVoNSMf3tuybGwJgCa0cjdQ

Swarm announcing /ip4/73.206.115.127/udp/4001/quic-v1

Swarm announcing /ip4/73.206.115.127/udp/4001/quic-v1/webtransport/certhash/uEiAAp-ODgPfpKxlNjFQcsI43HD1LRoRY5ULwgDYCVoFK0w/certhash/uEiCJdPZ3OUjyS9v9MX7zAodgVoNSMf3tuybGwJgCa0cjdQ

RPC API server listening on /ip4/127.0.0.1/tcp/5001

WebUI: http://127.0.0.1:5001/webui

Gateway server listening on /ip4/127.0.0.1/tcp/8080

Daemon is ready

Connection to localhost (127.0.0.1) 3000 port [tcp/*] succeeded!

Connection to localhost (127.0.0.1) 3001 port [tcp/*] succeeded!

Connection to localhost (127.0.0.1) 4001 port [tcp/*] succeeded!

[ls.io-init] done.

node:internal/process/promises:279

            triggerUncaughtException(err, true /* fromPromise */);

            ^

[Error: EACCES: permission denied, mkdir '/data/nds/backgrounds'] {

  errno: -13,

  code: 'EACCES',

  syscall: 'mkdir',

  path: '/data/nds/backgrounds'

}

Connection to localhost (127.0.0.1) 3000 port [tcp/*] succeeded!

andres125correa avatar Feb 18 '24 02:02 andres125correa

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

github-actions[bot] avatar Feb 18 '24 02:02 github-actions[bot]

Found a fix , just went to the container and chmod the /data path wide open . So there seems to be a permission issue on the latest release ?

andres125correa avatar Feb 18 '24 03:02 andres125correa

Don't mount in roms like that please read the readme, I would start over and clear out your current data directory.

thelamer avatar Feb 18 '24 03:02 thelamer

Don't mount in roms like that please read the readme, I would start over and clear out your current data directory.

Where on the read me it talks about how to mount the roms ? On most of other tutorials are done like this , and what I understood from the readme is to place the path like that.

andres125correa avatar Feb 18 '24 04:02 andres125correa

Don't mount in roms like that please read the readme, I would start over and clear out your current data directory.

Do I add the :ro at the end of my paths ? do I need to start over or just modify it like that the stack ?

andres125correa avatar Feb 18 '24 05:02 andres125correa

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

LinuxServer-CI avatar Mar 20 '24 04:03 LinuxServer-CI

This issue is locked due to inactivity

github-actions[bot] avatar Jun 18 '24 05:06 github-actions[bot]