a3x/gnutella-gtk-docker
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
gnutella-gtk and Xvfb automatically built in a docker container
6 commits 1 branch 0 tags 23 KiB
Dockerfile 66.2%
Shell 33.8%
Go to file
James May f79ed8fafa Merge branch 'master' of https://git.eris.cc/a3x/gnutella-gtk-docker
2021-04-26 01:33:18 +02:00
docker Merge branch 'master' of https://git.eris.cc/a3x/gnutella-gtk-docker 2021-04-26 01:33:18 +02:00
.gitignore Now it's webby 2021-04-26 01:29:16 +02:00
docker-compose.yml Now it's webby 2021-04-26 01:29:16 +02:00
README.md Now it's webby 2021-04-26 01:29:16 +02:00

README.md

Intro

Running a gtk-gnutella instance in docker, build from latest source and accessible via IPC-socket over SOCAT (see usage) or VNC.

Usage

Make sure all mounted volumes under /app are owned by 1000:1000.

VNC

You can conenct and control your instance via given VNC port and password in docker-compose.yml.

NoVNC

You can also access the VNC Interface via NoVNC WebInterface on port 5800

IPC over socat

You connect to the gtk-gnutella daemon via IPC over TCP. You need to have socat and gtk-gnutella on your client too.

1.:

sudo socat UNIX-LISTEN:/home/user/local.socket,fork TCP-CONNECT:<REMOTE_HOST>:8089

2.:

gtk-gnutella --shell /home/user/local.socket

Notes

In both cases I strongly recommend using a VPN and not running either VNC or IPC over the internet. Especially the "IPC over socat" hack is truly dangerous when listening on outward facing interfaces since there is no protection at all.