Creating recipe and docker daemon not exposing my ports #410

New Issue

2023-02-13T06:14:07Z

codegod100 commented

2023-02-13 06:14:07 +00:00

Where is the best place to look for how abra interacts with docker daemon? I have deployed my recipe I'm working on with abra and I can attach to the container and app is running on localhost but the daemon is not exposing the ports and when I vist app url there is no display.

codegod100 added the bug label 2023-02-13 06:14:07 +00:00

codegod100 commented

2023-02-13 06:17:34 +00:00

Here is my compose file because you'll prolly ask for it

---
version: "3.8"

services:
  app:
    image: moonlion/agora-server
    volumes:
      - data:/home/root/agora
    networks:
      - proxy
    environment:
      - STACK_NAME
    deploy:
      labels:
        - "traefik.enable=true"
        - "traefik.docker.network=proxy"
        - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=5017"
        - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
        - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
        - "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect"
        - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true"
        - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}"
        - coop-cloud.${STACK_NAME}.version=0.5.0+1.9.6
  bridge:
    image: moonlion/agora-bridge
    volumes:
      - data:/agora-bridge
volumes:
  data:
networks:
  proxy:
    external: true
  internal:

Here is my compose file because you'll prolly ask for it ``` --- version: "3.8" services: app: image: moonlion/agora-server volumes: - data:/home/root/agora networks: - proxy environment: - STACK_NAME deploy: labels: - "traefik.enable=true" - "traefik.docker.network=proxy" - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=5017" - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}" - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure" - "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect" - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true" - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}" - coop-cloud.${STACK_NAME}.version=0.5.0+1.9.6 bridge: image: moonlion/agora-bridge volumes: - data:/agora-bridge volumes: data: networks: proxy: external: true internal: ```

codegod100 commented

2023-02-13 06:19:03 +00:00

As you can see in the compose my app runs on port 5017 but when I docker ps there is no exposed port showing as there is with every other app I have deployed with abra. Not sure where the breakdown is

As you can see in the compose my app runs on port 5017 but when I `docker ps` there is no exposed port showing as there is with every other app I have deployed with abra. Not sure where the breakdown is

decentral1se commented

2023-02-13 07:29:11 +00:00

Ah @codegod100, 5017 won't be exposed to the host but will be available on the proxy network for treafik to route requests from port 80/443 to. Do you have traefik deployed alongside your app? Treafik can be a bit of a black box but usually it will complain if it can't route your app. If you're running a localhost deployment with no requirements for TLS and such, then I think Traefik supports this but that is getting into "haven't tried this before, no idea what you'll face" mode.

Ah @codegod100, `5017` won't be exposed to the host but will be available on the `proxy` network for `treafik` to route requests from port `80`/`443` to. Do you have `traefik` deployed alongside your app? Treafik can be a bit of a black box but usually it will complain if it can't route your app. If you're running a localhost deployment with no requirements for TLS and such, then I think Traefik supports this but that is getting into "haven't tried this before, no idea what you'll face" mode.

decentral1se commented

2023-02-13 07:30:12 +00:00

FYI a simple/short into guide for Traefik is https://dockerswarm.rocks/traefik/

codegod100 commented

2023-02-13 08:12:43 +00:00

You said 5017 won't be exposed to the host but will be available on the proxy network for treafik to route requests from port 80/443 to.

I get how this makes sense, however when I look at docker ps all the other apps have ports exposed so while I believe you, the anamalous behaviour is suspicious.

You said `5017 won't be exposed to the host but will be available on the proxy network for treafik to route requests from port 80/443 to. ` I get how this makes sense, however when I look at `docker ps` all the other apps have ports exposed so while I believe you, the anamalous behaviour is suspicious.

😆 1

codegod100 closed this issue

2023-02-13 08:13:15 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#410