Update!!

Published two packages to Hex today:

1. ex_docker_engine_api | Hex (there is excontainers and docker_engine_api but both of these are useless as I need something stable to depend on)
2. testcontainers | Hex

The latter being the interesting one

Im crossing fingers that some might find it useful! I have committed to this project, and I’m ready for all the weird corner cases.

Maybe you want to join in on the fun and improve on it? You are welcome!

Update

Just released a new feature

You can now use testcontainers with MySql adapter for ecto too

The plan is to increase the number of supported databases for use with ecto.

Right now the plan is to add more containers, among them mongodb, including ecto support for it. And other commonly used databases with Phoenix.

(Big?) Update

v1.2.3 is released.

It fixes a glaring issue about container cleanup, that caused parallell test runs to fail each other in random ways.

I needed to do some huge refactor of the library, internally, which didn’t added breaking changes in the api, luckily.

But for ExUnit and disposable containers inside the tests, you must now add

Testcontainers.start_link()

in test/test-helper.exs

This is not needed if using the Testcontainers.Ecto module, which can be dropped into application.ex as shown in the readme.

I considered making a minor version change, but this only fixes bugs and discrepancies.

I have successfully moved away from the silly idea of using macro function and the library is now using plain old functions to do the grunt work. I have also successfully managed to test an nginx container with the library, even to get the whole welcome from nginx index page asserted in the test.

So whats on todo now ? Wait for log statement logic. I have wait for port and wait for http. Waiting for log statement match is the next step. then everything from there is just mapping keywords in elixir to docker engine api request structs. Conceptually easy, but not trivial in practice of course

A big item on the todo list, is the “get docker base url” logic that I have currently glossed over in my library. Im just using a hard coded http+unix:// url which works on Mac and Linux, but not Windows. So if anyone want to get their hands dirty on elixir code you are welcome to join in. Code will be reviewed and we will learn something new

I didn’t even know how docker engine api worked before I start

Update:

560 lines of elixir code in the lib folder in the project now, and I can already start using it, albeit with git reference in mix. Im beginning to get confident about publishing it to Hex soon, just need to add some more tests. Any good name suggestions is appreciated, but if not I’ll just go for testcontainers_elixir. Dont need any fancy naming conventions.

There is only one macro file in the project now, and that is a ex_unit.ex macro file that contains macros for injecting exunits on_exit callback function into the Docker.Api.run method. Other than that the code is basically pretty much magic free. I haven’t yet added type specs everywhere because I really hate all the false positives. But it will come at some point.