Skip to content

Release 1.15.0-rc2 contains conflicts with another lib #3341

Closed

Description

@asulyma

Fixed in #3159 and released in 1.15.0-rc2

There are conflicts with org.jetbrains.annotations lib. Version: 20.1.0

image

After move back version of testcontainers to 1.14.3 - everything is ok.

Activity

  1. bsideup commented on Oct 13, 2020

    @bsideup
    Member

    It does not seem to "conflict". The library is now compileOnly, which is absolutely valid since, on JVM, the class will load fine even if some of the annotations are missing on classpath.

  2. asulyma commented on Oct 13, 2020

    @asulyma
    Author

    Thanks for the fast support.
    I've made some workaround for the jetbrains lib, but now I catch the following error with initialization:
    image
    image

    Full error message:

    Caused by: java.lang.IllegalStateException: Failed to verify that image 'mdillon/postgis:10' is a compatible substitute for 'postgres'. This generally means that you are trying to use an image that Testcontainers has not been designed to use. If this is deliberate, and if you are confident that the image is compatible, you should declare compatibility in code using the asCompatibleSubstituteFor method. For example:
    DockerImageName myImage = DockerImageName.parse("mdillon/postgis:10").asCompatibleSubstituteFor("postgres");
    and then use myImage instead.

    I tried to use DockerImageName.parse(), but after that, I can't use variables from PostgreSQLContainer, and also it provides more code changes that I expected.

    Is it expected?
    One more additional details, I tried to downgrade the version of testcontainers to 1.14.0 and 1.14.2 but catch the following exception:

    Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=mdillon/postgis:10, imagePullPolicy=DefaultPullPolicy())
    Caused by: java.lang.IllegalStateException: Can not connect to Ryuk

    (if it will be useful - I use Ubuntu 20.04)

  3. asulyma commented on Oct 14, 2020

    @asulyma
    Author

    Resolved manually via an added workaround: network_mode: host to docker-compose file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    resolution/waiting-for-infoWaiting for more information of the issue author or another 3rd party.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions