Considering migrating to testcontainers

[stormshield-gt]

I have the following problems with the dockertest-server used in the test suite:

• it's no longer maintained
• it force users to disconnect from VPN to launch the test suite, which is quite annoying (otherwise we get this error)
• it's not possible to run all the tests locally (Bind for 127.0.0.1:8300 failed: port is already allocated), I'm obligated to run only a subset

I've successfully used testcontainers with Vault at work and it's really easy to setup. I see a lot of advantages

• maintained
• supports setting up multiple containers, so we can continue to spawn additional docker (ex AWS)
• works if a VPN is activated
• tests are parallelized using different ports so it should also give a significant speedup to the test suite

[Haennetz]

If I understand the stack overflow thread correct the VPN issues root cause is that the VPN network segment overlaps with that one docker chooses. The solution for that would be to specify the range for the docker networks outside the range by the VPN see.

If I understand the documentation of testcontainers correct we have to add a vault module for the vault container?

[stormshield-gt]

If I understand the stack overflow thread correct the VPN issues root cause is that the VPN network segment overlaps with that one docker chooses. The solution for that would be to specify the range for the docker networks outside the range by the VPN see.

You are right I could get away with a configuration, but the point is that with testcontainers I don't have to.

If I understand the documentation of testcontainers correct, we have to add a vault module for the vault container?

There is already an existing one

It's also really easy to define one locally, I've been used a one tailored to our production needs for months now.

[Haennetz]

If you want to, you can prepare a pull request to use testcontainers