TestContainers Java has the concept of modules.
Those modules are reusable and pre-defined Container for popular projects.
I don't think we are ready to do the same for Go just yet. I proposed a similar
canned, mainly to avoid misunderstanding with Go
Submodules in Go are not easy to maintain today and I want to keep testcontainers dependencies under control and the project light. If we start merging modules as part of the main repository we will get one dependency at least for each of them. This will blow up quickly adding overheard to the maintainers of this project as well.
Share your modules
I know it is important to share code because it makes a project battle tested. You can create your own modules and you can list them here, in this way other users will be able to import and reuse your work and experience in the meantime that we figure out a better solution based as well on how many modules we will get.