Jens Reimann
Jens Reimann
> Indeed the locks are the biggest pain here and I expect they are the cause of the last issue I'm seeing (the client sometimes hanging after running fine for...
> I think the path started here is reasonable. Absolutely! And I didn't want to discourage you from doing so!
> The name of the container can be set per `run` invocation using `RunArgs`. You can thus provide individual names to containers of the same image. Does that not work...
I see your point. I am not sure, though if removing an existing parameter is a good idea :) But I also don't see any real reason to use a...
> What is the usecase in which you would have needed a timeout? The issue I ran into is that it looks like Postgres containers fail to start up properly...
> I am leaning towards a global one that can maybe be overridden through an env variable to keep the images themselves simple. Sounds reasonable to me. If additional requirements...
Sure, I am not a podman expert, but I can try to look into it.
This looks like an issue with `podman logs -f` in case a container is already terminated/completed.
> I guess we just need to wait now until podman releases a new version and GitHub's virtual environment ships that version. Yes, I hope that will be soon.
Is there any update on this?