Reports

oblivisheee. I little a bit modified your compose config to build and start this docker service by itself, without requiring a surrealdb, a redis, a loki and a nats services. My compose config looks like:

services:
  assistant:
    image: ghcr.io/kiroshi-ai/kiroshi-ai-assistant:v1
    build:
      context: ./assistant
      context: .
      dockerfile: Dockerfile
      dockerfile_inline: |
        FROM debian:bookworm
    ports:
      - "3500:3500"
    depends_on:
      - surrealdb
      - redis
      - loki
      - nats

    command:
      - sleep
      - "3600"

    dns:
      - 8.8.8.8
      - 8.8.4.4
      - 1.1.1.1
      - 9.9.9.9
      - 168.63.129.16
      - 20.62.61.128
      - 20.98.195.77
      - 84.200.69.80
      - 8.26.56.26
      - 208.67.222.222
      - 10.254.254.254
    extra_hosts:
      - "host.docker.internal:host-gateway"
    networks:
      - default
      - db
      - logs
      - nats
      - nginx



networks:
  default:
    driver: bridge
  db:
    name: kiroshi-ai-db-network
  logs:
    name: kiroshi-ai-logs-network
  nats:
    name: kiroshi-ai-nats-cluster
  nginx:
    name: kiroshi-ai-nginx-network

So, in general, your compose service has access to the global network. I checked it the next way:

docker compose up -d to build and start the service
docker compose exec -it assistant sh to go into the container environment
apt update && apt install -y iputils-ping to install the ping utilite
Finally, check the access to the api from a runnig container:

# ping amazon.com
PING amazon.com (205.251.242.103) 56(84) bytes of data.
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): icmp_seq=1 ttl=230 time=202 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): icmp_seq=2 ttl=230 time=222 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): icmp_seq=3 ttl=230 time=245 ms
^C
--- amazon.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 202.095/223.137/245.254/17.635 ms

Try to reproduce, and if you still haven't access to the amazon.com from docker, check do you have access to amazon from the host system.

79333180