docker-compose.yml

version: "3.7"
services:
    i2pd: 
        image: geti2p/i2p
        hostname: i2pd
        networks:
            i2p_net:
                ipv4_address: 172.16.200.10
                aliases:
                    - i2pd
    contained:
        build:
          context: contained/
        hostname: contained
        # Required for [iptables]
        cap_add:
            - NET_ADMIN
            - NET_RAW
        depends_on:
            - i2pd
        volumes:
            - /tmp/contained:/mount
        networks:
            i2p_net:
                ipv4_address: 172.16.200.20
                aliases:
                    - contained

networks:
    i2p_net:
        driver: bridge
        ipam:
            config:
                - subnet: "172.16.200.0/24"

# iptables: https://stackoverflow.com/questions/41706983/installing-iptables-in-docker-container-based-on-alpinelinux
Attempt at forwarding all traffic through an HTTP proxy DNS doesn't work so there was an attempt at just forcing stats.i2p to localhost, with no success. A tcpdump is created on the host machine at /tmp/contained/tcp.dmp to try and figure out what is being sent where, but it doesn't seem like any HTTP traffice is being sent at all. `iptables` is logged to /var/log/ so maybe that'll give a hint as to where the stuff is going. Maybe the rules are just bad too 🤷‍♂ 2019-07-20 21:25:00 +02:00			`version: "3.7"`
			`services:`
			`i2pd:`
Use java i2p since there seems to be a problem with i2pd and proxies #1 - Forward using iptables, pr0xy and custom DNS 2019-07-27 23:06:01 +02:00			`image: geti2p/i2p`
Attempt at forwarding all traffic through an HTTP proxy DNS doesn't work so there was an attempt at just forcing stats.i2p to localhost, with no success. A tcpdump is created on the host machine at /tmp/contained/tcp.dmp to try and figure out what is being sent where, but it doesn't seem like any HTTP traffice is being sent at all. `iptables` is logged to /var/log/ so maybe that'll give a hint as to where the stuff is going. Maybe the rules are just bad too 🤷‍♂ 2019-07-20 21:25:00 +02:00			`hostname: i2pd`
			`networks:`
			`i2p_net:`
			`ipv4_address: 172.16.200.10`
			`aliases:`
			`- i2pd`
			`contained:`
Move contents for contained image into contained dir We don't wanna pollute the root dir with files pertaining to the contained image #1 - Forward using iptables, pr0xy and custom DNS 2019-07-24 13:41:57 +02:00			`build:`
			`context: contained/`
Attempt at forwarding all traffic through an HTTP proxy DNS doesn't work so there was an attempt at just forcing stats.i2p to localhost, with no success. A tcpdump is created on the host machine at /tmp/contained/tcp.dmp to try and figure out what is being sent where, but it doesn't seem like any HTTP traffice is being sent at all. `iptables` is logged to /var/log/ so maybe that'll give a hint as to where the stuff is going. Maybe the rules are just bad too 🤷‍♂ 2019-07-20 21:25:00 +02:00			`hostname: contained`
			`# Required for [iptables]`
			`cap_add:`
			`- NET_ADMIN`
			`- NET_RAW`
			`depends_on:`
			`- i2pd`
			`volumes:`
			`- /tmp/contained:/mount`
			`networks:`
			`i2p_net:`
			`ipv4_address: 172.16.200.20`
			`aliases:`
			`- contained`

			`networks:`
			`i2p_net:`
			`driver: bridge`
			`ipam:`
			`config:`
			`- subnet: "172.16.200.0/24"`

			`# iptables: https://stackoverflow.com/questions/41706983/installing-iptables-in-docker-container-based-on-alpinelinux`