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

Bad gateway and no logs with minimal traefik setup #157

Open
hood opened this issue Feb 26, 2024 · 1 comment
Open

Bad gateway and no logs with minimal traefik setup #157

hood opened this issue Feb 26, 2024 · 1 comment

Comments

@hood
Copy link

hood commented Feb 26, 2024

Hi, with the following super minimal docker-compose.yaml setup, with the service getting exposed through Traefik, hitting the server via http returns me a 502 bad gateway error, and I’m getting no error logs in registry’s dedicated container. Any ideas why?

version: '3.9'

services:
  myregistry:
    image: registry:2
    environment:
      REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: /data
    volumes:
      - ./data:/data
    restart: always
    ports:
      - 5000:5000
    networks:
      - proxy
      - default
    labels:
      traefik.enable: true
      traefik.docker.network: proxy
      traefik.http.routers.docker-registry-secure.entrypoints: websecure
      traefik.http.routers.docker-registry-secure.rule: Host(`myregistry.mydomain.tld`)
      traefik.http.services.docker-registry-secure.loadbalancer.server.port: 5000

networks:
  proxy:
    external: true
@milosgajdos
Copy link
Member

I'm not familiar with how traefik works, I'm afraid but I'd expect traefik to log something when the upstream server fails to respond for whatever reason. I'd also suggest opening this in the discussions (https://github.com/distribution/distribution-library-image/discussions/landing) instead of as a GH issue.

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