Roland Huß
Roland Huß
Thanks for your investigation! > I'm still very confused about the error message "Container stopped with exit code null unexpectedly" Indeed, for me it smells like that there is confusion...
It's mentioned in the [documentation](https://dmp.fabric8.io) * `autoRemove` is an option for `docker:start` and indicates that the container should be removed if it stops (on its own). * `docker:stop` stops and...
afair, there is nothing like a `docker.runArg` property according to https://dmp.fabric8.io/#property-configuration I think you should try `docker.envRun.http_proxy` in your case, if you want to set the `http_proxy` env var when...
If this help, please feel free to close this issue.
Yes, that probably would make sense
The problem is that in `library.go`, the `isStdlib()` function checks whether a package is stored below GOROOT or not, and if so, it is considered to be a standard library...
The solution would be to fix `isStdLib()` to respect toolchains to be stored outside of `GOROOT`.
Some additional context: * The issue only hits you if you are using another toolchain than the one bundled without your go installation. * You can always force to use...
You could add a `toolchain default` to your go.mod file. In the end, it's a lottery ;-) If your local go installation is the same or newer than any specified...
I really love the idea and this is definitely a start in the right direction. I guess such a `ContainerSource` could also be used in a `SinkBinding` (i'm always confused...