10000 When not using elasticsearch, the port is still binded during unit test · Issue #55 · localstack/localstack-java-utils · GitHub
[go: up one dir, main page]

Skip to content
When not using elasticsearch, the port is still binded during unit test #55
Open
@feguiguren

Description

@feguiguren

In my test, I only use S3 service, with this annotation:

@ExtendWith(LocalstackDockerExtension.class) @LocalstackDockerProperties( portEdge = "4577", services = {"s3"}, hostNameResolver = HostResolver.class)

I configured the edge port because I have multiple tests running on the same runner at the same time, but they fail because the elasticsearch port is already binded by another test suite.

[error] docker: Error response from daemon: driver failed programming external connectivity on endpoint hopeful_fermi (a98226257cb706ef22f296a7cb04d3b0ce148d1f013f251f57dd38a9c2cfe668): Bind for 0.0.0.0:4571 failed: port is already allocated.

If I am not using elastic search, I think the port should not be in use.

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

      0