t-chab / dockerfiles Goto Github PK

Tks for composing the docker image. Yet I was not able to enter the web UI after installation on a Synology NAS device.
It simply prompts me with a logon window, awaits my password input.

Being a novice Synology user without Linux/Unix exposure, I cannot find the config file for aMule in the docker.

Is there a default password for this? Tks for any help in advance.

Below is my defalt setting:

amule: shouldn't port 4711 be mapped instead of 4712?

Please help on the following error:

$ docker run -p 4711:4711 -p 4662:4662 -p 4672:4672/udp -e WEBUI_PWD=p455w0rd -e GUI_PWD=p455w0rd -v ~/.amule/conf:/home/amule/.aMule -v ~/.amule/incoming:/incoming -v ~/.amule/tmp:/temp tchabaud/amule
/home/amule/.aMule/amule.conf file found. Using existing configuration.
/home/amule/.aMule/remote.conf file found. Using existing configuration.
 2019-03-07 14:17:23: Logging to stdout enabled
 2019-03-07 14:17:23: Initialising aMuleD 2.3.2 compiled with wxBase(GTK2) v2.8.12 (Snapshot: rev. g5d9c1f458)
!2019-03-07 14:17:23: ERROR: Fatal error. Permissions on the configuration directory too strict!
!2019-03-07 14:17:23: aMule cannot proceed. To fix this, you must set read/write/exec
!2019-03-07 14:17:23: permissions for the folder '/home/amule/.aMule/'

Hi, now I had another problem. Once connected the connection immediately becomes slow and I cannot navigate both with ameleweb and amulegui. Has anyone else had this problem?

I have an error when launching the docker-compose with your image. Everything goes well except the last line, that aborts the execution of amule.sh and makes amule container to infinite loop restart: (this is the second execution, in the first the user and group are created correctly, so that now is showing they will not be created)

Group 101 already exists. Won't be created.
Group amule with GID 101 will be used as amule group.
User 1026 already exists. Won't be added.
/home/amule/.aMule/amule.conf file found. Using existing configuration.
/home/amule/.aMule/remote.conf file found. Using existing configuration.
2019-03-24 21:32:42: Logging to stdout enabled
--== cannot generate backtrace ==--

A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/index.php?board=67.0
If possible, please try to generate a real backtrace of this crash:
http://wiki.amule.org/wiki/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuleD 2.3.2 compiled with wxBase(GTK2) v2.8.12 (Snapshot: rev. g5d9c1f458)
Running on: Linux 3.10.105 x86_64

/home/amule/amule.sh: line 274: 21 Aborted sudo -H -u "#${AMULE_UID}" sh -c "amuled -c ${AMULE_HOME} -o"

Thanks for providing the container!

I am doing a research aiming at finding issues in configuration files. After pulling the image we notice that ServerName is set to www.example.com:443 in etc/apache2/conf.d/ssl.conf and ServerAdmin is set to [email protected] in /etc/apache2/httpd.conf.

However, the HttpD official document recommends the following config:

• ServerName : "For optimal reliability and predictability, you should specify an explicit hostname and port using the ServerName directive."
• ServerAdmin: "However, it's recommended to actually use an email address, since there are a lot of CGI scripts that make that assumption. "

Could you please provide a knob to specify the value of ServerName and ServerAdmin to identify yourself?

Amule 2.3.3 is released after 4 years.

https://github.com/amule-project/amule/releases/tag/2.3.3

Hi, I've tried to move a current installation to a docker container.

It seems to work everything except for the web UI password.
I've passed it as an environment variable as described but when I write it and then try to login it doesn't login.

In the logs I can't see anything useful.

addgroup: group 'amule' in use
adduser: user 'amule' in use
/home/amule/.aMule/amule.conf file found. Using existing configuration.
/home/amule/.aMule/remote.conf file found. Using existing configuration.
2018-04-05 17:39:29: Logging to stdout enabled
2018-04-05 17:39:29: Initialising aMuleD 2.3.2 compiled with wxBase(GTK2) v2.8.12 (Snapshot: rev. g5d9c1f458)
2018-04-05 17:39:29: Checking if there is an instance already running...
2018-04-05 17:39:29: No other instances are running.
!2018-04-05 17:39:29: ERROR: Error accessing directory. Permissions on the temp directory too strict!
!2018-04-05 17:39:29: aMule cannot proceed. To fix this, you must set read/write/exec
!2018-04-05 17:39:29: permissions for the folder '/temp'
!2018-04-05 17:39:29: Attempting to use default directory at location
!2018-04-05 17:39:29: '/home/amule/.aMule/Temp'.
2018-04-05 17:39:29: Creditfile loaded, 2386 clients are known
2018-04-05 17:39:29: *** TCP socket (ECServer) listening on 0.0.0.0:4712
2018-04-05 17:39:29: Created Server UDP-Socket at port 4665
2018-04-05 17:39:29: ListenSocket: Ok.
2018-04-05 17:39:29: Created Client UDP-Socket at port 4672
2018-04-05 17:39:29: Loading server.met file: /home/amule/.aMule/server.met
!2018-04-05 17:39:29: 20 servers in server.met found
2018-04-05 17:39:29: Loading temp files from /home/amule/.aMule/Temp.
2018-04-05 17:39:29: All PartFiles Loaded.
2018-04-05 17:39:29: No part files found
2018-04-05 17:39:29: No shareable files found in directory: /incoming
2018-04-05 17:39:29: Found 0 known shared files
!2018-04-05 17:39:30: web server running on pid 31
2018-04-05 17:39:30: amuled: OnInit - starting timer
2018-04-05 17:39:30: Loading IP filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2018-04-05 17:39:30: Loaded 0 IP-ranges from '/home/amule/.aMule/ipfilter.dat'.
2018-04-05 17:39:30: Loaded 0 IP-ranges from '/home/amule/.aMule/ipfilter_static.dat'.
2018-04-05 17:39:30: IP filter is ready
!2018-04-05 17:39:30: Connecting
2018-04-05 17:39:30: Connecting to eDonkey Server No2 (176.103.56.135 - 176.103.56.135:2442) using protocol obfuscation.
2018-04-05 17:39:30: Read 166 Kad contacts
!2018-04-05 17:39:30: Kad started.
2018-04-05 17:39:30: New external connection accepted
!2018-04-05 17:39:30: Kad stopped.
!2018-04-05 17:39:30: Connected to Kad (firewalled)
2018-04-05 17:39:30: Connecting client: aMuleweb 2.3.2
2018-04-05 17:39:30: Access granted.
2018-04-05 17:39:30: Connected to eDonkey Server No2 (176.103.56.135:2442)
2018-04-05 17:39:30: Connecting to eMule Security (80.208.228.241 - 80.208.228.241:8369) using protocol obfuscation.
2018-04-05 17:39:30: Connected to eMule Security (80.208.228.241:8369)
!2018-04-05 17:39:31: Connection established on: eMule Security
!2018-04-05 17:39:31: Connected to eMule Security with HighID
2018-04-05 17:39:31: New clientid is 3306683284
2018-04-05 17:39:31: ServerMessage: server version 17.15 (lugdunum)
2018-04-05 17:39:31: ServerMessage: Welcome to eMule Security! <> www.emule-security.org
2018-04-05 17:39:31: ServerMessage: Download Safe Serverlist > http://www.emule-security.org/serverlist/
2018-04-05 17:39:31: ServerMessage: IP-filter > http://www.emule-security.org/e107_plugins/faq/faq.php?0.cat.2.1
2018-04-05 17:39:31: ServerMessage: nodes.dat > http://www.emule-security.org/e107_plugins/faq/faq.php?0.cat.6.6

Any guess on what could be wrong?

Hello,

I would like to use your dockerfile for amule, but I has to change the user ID and group ID to another number to be able to write on my NAS using my actual configuration. At this moment, your docker image force amule process to run under UID 5000 and GID 5000.

For example, LinuxServer/nzbget does allow it by using environment variables for PUID and PGID, which means "Process User/Group ID".

Is it possible to implement this kind of configuration in your repo?

Thanks,
Best regards

Since synopsis8 has been outdated for several years => https://github.com/synopsis8/dockerfiles/tree/master/amule
Could you link to my repository instead? It supports many architectures. I have been maintaining it for more than a year and I will do in the future since I use it in my NAS.

https://github.com/ngosang/docker-amule

How can I select a folder for shared files for amule?

Hello! With the latest image amule has been broken for me:

/home/amule/amule.sh: set: line 7: illegal option -E
/home/amule/amule.sh: set: line 7: illegal option -E

If I edit the file amule.sh on the overlay filesystem and comment line 7, another error appears:

sudo: unknown user: 5000
sudo: unable to initialize policy plugin

Do you know what can be wrong? Thank you!

Thank you very much for creating docker image for amule. I have (hopefully) basic problem, but I cannot resolve it. I used scenario when I have already "old" amule setup i.e.:

docker run -p 4711:4711 -p 4662:4662 -p 4672:4672/udp \
    -e PUID=[wanted_uid] -e PGID=[wanted_gid] \
    -v ~/.aMule:/home/amule/.aMule -v ~/.aMule/Incoming:/incoming -v ~/.aMule/Temp:/temp tchabaud/amule

Which resulted with error:

2020-09-05 15:47:14: Dropping non-existing shared directory: /home/mist/.aMule/Incoming
2020-09-05 15:47:14: Error: Directory '/home/mist/.aMule/Temp' couldn't be created (error 2: No such file or directory)
!2020-09-05 15:47:14: ERROR: Error accessing directory. Could not create the temp directory at '/home/mist/.aMule/Temp'.

"mist" is my user and the location is correct. Hmm, in my case ".aMule" is in fact a symlink, so I thought maybe this is a problem, so I entered the real directory when launching docker. And I got the same result.

Ok, so I renamed my local .aMule directory, and run docker again. With the same result.

So in total those attempts caused two question:

• how to map my local filesystem, so docker container could see it and work with it
• second, how it is possible that even when I changed the local directories in docker call, it still shows an error against "~/.aMule" (in theory it should not be possible, because container does not know anything about local filesystem), only docker itself knows about it, and I changed the call

For the record my call (wrapped as script) is this:

AMULE_DIR=~/.shared/.aMule
docker run -p 4711:4711 -p 4662:4662 -p 4672:4672/udp -e PUID=$(id -u) -e PGID=$(id -g) -v $AMULE_DIR:/home/amule/.aMule -v $AMULE_DIR/Incoming:/incoming -v $AMULE_DIR/Temp:/temp tchabaud/

amule

Hi tchabaud,
running on Ubuntu 18.04.2 LTS I got this error:
standard_init_linux.go:190: exec user process caused "exec format error"

I was wondering if there is a particular reason why you build from source amule (and also some other dependencies).
Why not using the version already packaged in alpine linux?

https://pkgs.alpinelinux.org/packages?name=amule&branch=edge

Thanks for providing the container! I have a question about one httpd config:AuthnCacheContext.
It seems the official document recommends to change the default directory, which is conservative and not optimal. A better policy is to name the AuthnCacheContext for the password provider: for example a htpasswd file or database table.

Maybe it's better to set that to specify a context string for use in the cache keyin the comfig file? Thanks.

randomly the docker partially crash with

Command ''amuleweb' '--amule-config-file=/home/amule/.aMule/amule.conf'' with pid '28' has finished with status code '-1'

the docker still run but not accesible through web

Deploying through kubernetes

 containers:
      - image: tchabaud/amule
        imagePullPolicy: Always
        name: amule
        env:
        - name: PGID
          value: "1000400"
        - name: PUID
          value: "0"
        - name: WEBUI_PWD
          value: passwordHere
        - name: GUI_PWD
          value: passwordHere
        - name: WEBUI_TEMPLATE
          value: AmuleWebUI-Reloaded
 volumeMounts:
        - mountPath: /temp
          name: amule-temporals
        - mountPath: /incoming
          name: downloads
        - mountPath: /home/amule/.aMule
          name: config