WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

The Docker image conduktor/conduktor-console:1.36.2 always runs its internal application on port 8080, regardless of what port mapping is configured on the host. #181

@BhavyaMPatel

Description

@BhavyaMPatel

conduktor-console:

image: conduktor/conduktor-console:1.36.2
 ports:
   - "8080:8080"
 volumes:
   - conduktor_data:/var/conduktor

If an end user tries to remap the port like:

  - "8088:8088"

the container will not work, because the internal port is always 8080.
The only valid mapping is:

  - "8088:8080"

Users might assume that the internal port is configurable or matches the external port they define. This causes confusion and makes debugging harder when user try to access localhost:8088 and will get ERR_CONNECTION_REFUSED or related error.

Please update the documentation or add a comment/example in the template somthing like this, to avoide confusion.

Conduktor Console listens internally on port 8080. When customizing your host port, ensure the container port remains 8080. Example: 8088:8080

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions