Cheers Janek,

first of all I fixed the example, you can check out https://github.com/sbalnojan/batect-sample-python.

I have no idea whether the old postgres container supported access without credentials or I simply forgot to add it in. Now it does. The problem was that the db container actually shut down inbetween.

To see that behavior I added a healthcheck (which then fails, and you can then debug from thereon with the "no cleanup on failure option" from batect).

To your second question: I still enjoy batect! Really for the purpose it's built for which is slightly different from ksync and scaffold in my opinion.

ksync & scaffold are amazing tools that basically allow to develop "locally" but in the cloud. That's an amazing and really seamless experience.

However I still need to setup quite a few things to get this running, I still might want to develop locally (I usually do, not every container starts in the cloud), I still want to run tests locally etc.

All of that is encapsulated in batect in a way that is

1. really like a "./go script", really easy for any new developer to setup (only JVM and docker needed and GO)

2. I really enjoy the nature of batect as a "documentation through code". When I write different blog posts/ repositories I always use batect and thus try to ensure that everyone knows how to set this up in his system.

So I think both have their place. Cheers