-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On Gradle 6 and Corretto 11, container was successfully started but got a stack trace #207
Comments
Hello, thank you for reporting this issue! Could you please try to run the project in Gradle 5.6.2? And which version of our plugin are you using, please? Thanks! |
hi michal. this works up until gradle 5.6.4. i just tried 0.10.2 on gradle 6 but still got the stack trace. |
Thank you! I'm not able to reproduce this issue but the exception is clear - Groovy is not able to locate private |
In my case, if I run
To be able to have logs but to also have the posibility of running a standalone
It disables the logging and then runs the task. Then, when I want to get the containers running instead of calling composeUp (that breaks) I call
|
ComposeUp was instantiated as such:
Started containers:
The text was updated successfully, but these errors were encountered: