Missing ports

[barukh27]

Hi there!

I'm running a docker image using this docker-compose template:

version: "2.1"
services:
  amule:
    image: ngosang/amule
    container_name: amule
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Madrid
      - GUI_PWD=XXXX
      - WEBUI_PWD=XXX
      - MOD_AUTO_RESTART_ENABLED=true
      - MOD_AUTO_RESTART_CRON=0 6 * * *
      - MOD_AUTO_SHARE_ENABLED=false
      - MOD_AUTO_SHARE_DIRECTORIES=/incoming;/my_movies
      - MOD_FIX_KAD_GRAPH_ENABLED=true
      - MOD_FIX_KAD_BOOTSTRAP_ENABLED=true
    ports:
      - "4711:4711" # web ui
      - "4712:4712" # remote gui, webserver, cmd ...
      - "4662:4662" # ed2k tcp
      - "4665:4665/udp" # ed2k global search udp (tcp port +3)
      - "4672:4672/udp" # ed2k udp
    volumes:
      - /mnt/aMule/config:/home/amule/.aMule
      - /mnt/Donwloads:/incoming
      - /mnt/Temp:/temp
    restart: unless-stopped

The thing is that the container is running but I can't reach the webui. Portainer doesn't show the ports. If I restart the containers they appear for some time and then they drop.

What am I missing out?

Thank you for your help.

EDIT:

It seems that the container is restarting forever.

The logs say too: chown: /incoming: Operation not permitted

[barukh27]

Hi again,

I think I found a mistake in the docker-compose template I followed. The volume paths should be written in capital letters as in /Incoming or /Temp

[ngosang]

You don't have to change the ports. In Linux the paths are case-sensitive. /incoming and /temp must be in lower case. You have something wrong here => MOD_AUTO_SHARE_DIRECTORIES=/incoming;/my_movies The /my_movies path is not mounted as volume. The first time you starts aMule it takes a while until you can access the Web UI. My recommendation is that you start without sharing files to make sure it's working. https://github.com/ngosang/docker-amule#usage

[barukh27]

Thank you for your interest and help.

You don't have to change the ports.

I think I didn't do so. What do you mean by that?

In Linux the paths are case-sensitive. /incoming and /temp must be in lower case.

The funny thing though is that I changed them and now everything works.

You have something wrong here => MOD_AUTO_SHARE_DIRECTORIES=/incoming;/my_movies The /my_movies path is not mounted as volume.

I'll correct it. I'll erase the /my_movies path (I copied it from your template, JIC).

Thanks, once again, for your help.

The first time you starts aMule it takes a while until you can access the Web UI. My recommendation is that you start without sharing files to make sure it's working. https://github.com/ngosang/docker-amule#usage

[barukh27]

The problem persists.

I've changed the MOD_AUTO_SHARE_DIRECTORIES=/incoming;/my_movies to MOD_AUTO_SHARE_DIRECTORIES=/incoming

I've left:

• /mnt/aMule/config:/home/amule/.aMule
• /mnt/Donwloads:/incoming
• /mnt/Temp:/temp

The container deploys but the log gets stuck and reads: chown: /incoming: Operation not permitted And it doesn't work.

When I change - /mnt/Donwloads:/incoming to - /mnt/Donwloads:/Incoming The program runs and downloads stuff.

[ngosang]

You configuratiom is fine. You have to change the permissioms of the /mnt/Downloads in the host. Give it 777

[barukh27]

Thanks again.

I run sudo chmod -R 777 /mnt/Downloads and redeploy the container. The log sayschown: /incoming: Operation not permitted

IDK what to do.

[ngosang]

Paste the output ls -lah /mnt/Downloads

[barukh27]

total 256K
drwxrwxr-x 2 root dietpi 128K Oct 19 18:41 .
drwxrwxr-x 4 root dietpi 128K Oct 19 18:41 .

[barukh27]

I found the issue:

The volume I was using was exfat. So the permission management didn't work. I formatted the volume to NTFS and, now, everything works as expected.

Thank you for your help.