container-per-ip

Some thing so you can spin up a container per client ip

This works by spawning a new container based on the host address of a connecting client.

Concurrent tcp connections route to the same container, containers are removed when a timeout has elapsed since the last connection closed.

container-per-ip 
Ben Simms <ben@bensimms.moe>
Run a container per client ip

USAGE:
    container-per-ip [OPTIONS] <IMAGE>

ARGS:
    <IMAGE>
            The docker image to run for each ip

OPTIONS:
    -b, --binds <BINDS>
            Volume bindings to provide to containers

    -e, --env <ENV>
            Environment variables to set on the child container

        --force-pull
            Always pull the image on start

    -h, --help
            Print help information

    -n, --network <NETWORK>
            Set the docker network containers should be started in

    -p, --ports <PORTS>
            Ports to listen on
            
            The supported syntax for ports is: udp:53, tcp:8080:80 (outside:inside), tcp:5000-5100
            (range), tcp:5000-5100:6000-6100 (outside range - inside range)

        --parent-id <PARENT_ID>
            Specifies the unique id set in the container-per-ip.parent tag of spawned containers.
            
            By default, containers will be tagged with `container-per-ip.parent = <uuid>`
            If specified, containers will be tagged with `container-per-ip.parent =
            <container_tag_suffix>`

        --privileged
            Should the containers be started with the `--privileged` flag

    -t, --timeout <TIMEOUT>
            Timeout (seconds) after an IPs last connection disconnects before killing the associated
            container
            
            [default: 300]

Running in docker

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock --net=host -it nitros12/container-per-ip --help