mag37
mag37
> Removing one the `-e` flag seems to fix the issue. (Same with whole line.) Wonderful - thank you! That's the quickfix I needed and I'll try to reproduce this...
Superb thanks a lot for troubleshooting and reporting back. I'll push a hotfix in a minute. Will try to set up more testing environments to try to reproduce it. Someone...
> Seems like a broken pipe, yes; `xargs` keeps writing to it, but the pipe ain't listening anymore. > > So it sound like one of the `xargs` instances returned...
Closing this as it's stale and wont be worked on - as I've also read and been suggested to not use the `set -e` option.
This is somewhat similar to #159 which answers some of the background why this isn't an easy task to implement. I agree it would be nice with some more details...
~~I just did some quick checks - might be easier than it was previously to get some of this information at hand without multiple extra steps.~~ Did another take -...
As this is nothing I'll pursue currently - due to lack of time and lack of ground to build on - I'll close it.
You're correct and this is due to the command is targeting the specific container within the compose: `${DockerBin} ${CompleteConfs} ${ContEnvs} up -d ${ContName}` There was some reasoning for this that...
Sorry I haven't replied yet - I had some infrastructural issues with my test environments. I tried to dig in the history and now I wonder if it's just an...
> Justed tested this and it work: Happy to hear, I'll continue to do some more testing before I do any changes to main. > Now there is a follow...