New Container: Lowkey Vault

[nagyesta]

What is the new container you'd like to have?

I would like to implement a Lowkey Vault container (an Azure Key Vault emulator which already has .Net and Java Testcontainers modules).

Docker container: https://hub.docker.com/r/nagyesta/lowkey-vault
Docker configuration: https://github.com/nagyesta/lowkey-vault/tree/main/lowkey-vault-docker
Lowkey Vault can be very useful for projects which need direct integration with Azure Key Vault as it can enable local development and testing.

Why not just use a generic container for this?

Although the generic container can start the container, the configuration is far form trivial due to the fact that the container uses 2 ports and has some pitfalls we can help avoid with a custom container.

Other references:

I can provide a PR for this if you are okay with that...

[alexanderankin]

if you can put it with the azure stuff and not use any deprecated apis (might be a bit of a challenge lol) i would merge this i think.

[alexanderankin]

can you link to the other impls source code for easy review

[nagyesta]

Hi @alexanderankin ,

thanks, please find the links below, not sure how helpful they will be:

• Java: https://github.com/nagyesta/lowkey-vault/tree/main/lowkey-vault-testcontainers/src/main/java/com/github/nagyesta/lowkeyvault/testcontainers
• .Net: https://github.com/testcontainers/testcontainers-dotnet/tree/develop/src/Testcontainers.LowkeyVault

What do you mean by together with the Azure stuff? Azurite and CosmosDB each have a separate module...

[nagyesta]

Please find the changes in PR #949

[alexanderankin]

ok so for context im currently figuring out how to do separation since we are moving to uv, there is an issue about this... at some point a previous maintainer created a bunch of pypi packages so now i need to figure out this pep process to reclaim them or come up with another strategy. so that they are separate is bad news for me, i will be taking a look at how azurite is organized on java.

actually looking at your links, since you are self hosting the java container, im inclined to say you should self host the python one as well... python is way easier to publish than java.

[alexanderankin]

I see that, let me try to get you added to the testcontainer registry so that you show up when people google for "lowkey vault python testcontainers" and you get all the fame and fortune without my maintenance.

…

On Tue, Jan 6, 2026 at 6:07 PM Esta Nagy ***@***.***> wrote: *nagyesta* left a comment (testcontainers/testcontainers-python#948) <#948 (comment)> Please find the changes in PR #949 <#949> — Reply to this email directly, view it on GitHub <#948 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACECGJHPJEIFJR6HMIGH7AT4FQ52NAVCNFSM6AAAAACQ33FMISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJWGY3TOOBWGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nagyesta]

Hi @alexanderankin

Thanks for looking into this!

ok so for context im currently figuring out how to do separation since we are moving to uv, there is an issue about this... at some point a previous maintainer created a bunch of pypi packages so now i need to figure out this pep process to reclaim them or come up with another strategy. so that they are separate is bad news for me, i will be taking a look at how azurite is organized on java.

The Java version is grouping them in one module here. I think moving the containers together will not be easy because I assume it would mean a breaking change because of the rename but it would be possible.

Furthermore, I guess then every container would need to be very clean of any dependencies. For example the way the token is obtained in my PR here would drag in the Azure credentials even if they are not strictly needed by the other containers, only the code using them.

actually looking at your links, since you are self hosting the java container, im inclined to say you should self host the python one as well... python is way easier to publish than java.

I am afraid this is bad news for the both of us then because I am a Java guy and then I need to learn how to self-publish this module as well as maintain it most probably alone instead of doing it together with the community. Plus I am worried, that I will need to do the same for Go and JavaScript as well if I am similarly unlucky there. That would be a lot of effort for one person.

I see that, let me try to get you added to the testcontainer registry so
that you show up when people google for "lowkey vault python
testcontainers" and you get all the fame and fortune without my maintenance.

This part is easy at least, just need to add it here