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

services.<name>.ports.<index>.app_protocol incorrectly blocked as not allowed #733

Open
2 tasks done
campfred opened this issue Feb 12, 2025 · 0 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@campfred
Copy link

⚠️ Please verify that this bug has NOT been reported before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

Upon trying a compose manifest that had the long syntax implemented for exposing network ports, I came across a validation error.

This confused me as I was pretty sure I understood correctly the docker compose documentation about this.

So, I tried running my compose manifest with the actual docker compose command and it worked without complaints.

Then, when it was running, I switched back to Dockge to see if it would see it running and it was, but no logs could be seen as it was still complaining about the manifest being invalid.

👟 Reproduction steps

Try running the following manifest in Dockge.

services:
reverse-proxy:
    image: traefik:v3
    ports:
      - name: entrypoint-web
        target: 80
        published: 80
        app_protocol: http
      - name: entrypoint-websecure
        target: 443
        published: 443
        app_protocol: https

👀 Expected behavior

Dockge should run the compose manifest and start showing logs.

😓 Actual Behavior

Stack doesn’t start and an error is displayed instead.

validating /opt/stacks/traefik/compose.yaml  services.reverse-proxy.ports.0  Additional property app_protocol not allowed

Dockge Version

1.4.2

💻 Operating System and Arch

Fedora 40

🌐 Browser

Safari iOS 18.3.1

🐋 Docker Version

Docker-CE 27.5.1

🟩 NodeJS Version

No response

📝 Relevant log output

@campfred campfred added the bug Something isn't working label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant