you are absolutely right ofc. Im just too lazy to remember to install it 
aaand i dont care too much about metrics really to have use for it. But I should … 
so I +1 on ctop
jarlah
0
)
)
)
dimitarvp
I considered it several times but I am currently on a job search so not exactly very active.
Don’t give up, I am sure people are using your library with success.
1
jarlah
Big news 
Testcontainers for Elixir now has (rootless) podman support 
Read more here
I have had this nugget of a problem on my desk for quite some time now and its quite funny how easy it was to fix. The major problem was that I am not using podman myself. So had to test at work where they are using podman. And i have also added a github workflow to verify that everything works for both normal docker and podman.
Im very psyched about this because it opens for many more (security oriented) developers to start using the library 
Try it out and see how/if it works for you.
3
jarlah
a friendly and helpful github user that previously reported podman not working, got back to me and told me that it was still not working after the release. Well i brought in the big guns, virtualbox, and installed ubuntu 24 and podman and started podman.socket service in user mode. Confirmed the issue, fixed the bug and released v1.11.5 Thanks to github user kianmeng for this helpful testing.
4
jarlah
New release v1.13.0 of Testcontainers for Elixir brings real power to the library. I was very annoyed by not having the option to run my phoenix server without first starting a postgres container manually which is always a chore of keeping in sync with the migrations …
So now we can do stuff like
mix testcontainers.run setup --db-volume localdev
mix testcontainers.run phx.server --db-volume localdev
Old task mix testcontainers.test is still working. Its redirecting to the new task.
0
jarlah
jarlah
Found a bug btw, that led me down a rabbit hole to refactor the whole mix task setup to programmatically run tasks, not via System.cmd, which in turn solves so many other problems. So there will come a new version soon.
0
jarlah
New release v1.13.1 completely rewrites the mix task, going from System.cmd to Mix.Task.run. I have no idea why i didn’t make it like this when i first started out.
Now you can run tests like this:
MIX_ENV=test mix testcontainers.run test
and server or setup like before
mix testcontainers.run setup --db-volume localdev
mix testcontainers.run phx.server --db-volume localdev
I decided to throw semver out of the bus for this release, so if youre using the watch option, you should look into something else, implementing the watch functionality in some other way.
0
jarlah
Wow, august 2025, last comment.
Lots have happened people! Testcontainers for Elixir is now in a release candidate version v2.0.0-rc2
Meaning: no more flaky ryuk connection on startup of tests, ability to run tests fully offline with TESTCONTAINERS_PULL_POLICY=never (or in property file in home folder) and general improvements regarding cleanup.
Im psyched about it. Specifically because i have two apps in production that i very often use claude to pair program with and when claude has to retry because flaky ryuk connection or just .. gives up running tests ? nope, doesnt cut it.
So i really hope more of you Elixir devs will find it useful now. It still doesnt support docker in docker, but thats next on the agenda
2