Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect over docker network #718

Open
SplinterHead opened this issue May 16, 2023 · 1 comment
Open

Connect over docker network #718

SplinterHead opened this issue May 16, 2023 · 1 comment

Comments

@SplinterHead
Copy link

I'm trying to connect AriaNG to Aria2 over an isolated Docker netwotk (no ports exposed to the host).
I'm struggling to get it to connect, is there any reason to expect the ports are to be exposed?

Docker compose sample:

services:
  aria2:
    image: <self-built aria2 image>
    container_name: aria2
    networks:
      - aria
    ...
  aria-ng:
    image: <self-built ariang image>
    container_name: ariang
    networks:
      - public
      - aria
    ...

networks:
  public:
    external: true # Ingress from public internet via reverse proxy
  aria:
    external: true # Isolated network for communication between these two containers
@Checker8763
Copy link

You need to expose to port of the container of aria2 (expose 6800 in dockerfile).

Or configure exposing the default port in the docker compose file.

With exposing I don't mean binding it to a host port but just the docker directive.

If you don't expose a port the whole container is essentialy sealed off with no port open for other containers to connect to.

And what network driver are you using for the aria network?

If you chose a truely isolate network with driver none then they obviously can't connect either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants