Skip to content

Scraper created during onboarding does not work when running in docker with custom port bindings #21937

Open
@williamhbaker

Description

@williamhbaker

To reproduce, start influxd using docker with a custom port binding:

docker run -p 9086:8086 influxdb:latest

Then, go through the onboarding via the UI (accessed via http://localhost:9086 in this case) and chose "quick start" - this will result in a scraper being created. The scraper will be set up to use http://localhost:9086/metrics as the target, but this won't work, because for the server running inside the docker container http://localhost:9086 is not valid; it actually needs to be http://localhost:8086. Deleting the broken scraper and creating a new scraper with the URL http://localhost:8086/metrics works as expected.

It doesn't seem like there's a quick fix for this since it would involve the UI somehow knowing if it is a docker container or not. It may be viable to allow the user to customize/confirm their scraper URL as part of onboarding if they chose the quick start.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions