-
Notifications
You must be signed in to change notification settings - Fork 91
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
SVT:Cannot start application in container due pt write too long error #1746
Comments
Here's the Dockerfile that I used.
|
I get the same error when I try to run the mvn liberty:devc command from the command prompt as well.
|
This issue looks very similar, but had no solution. It just went away eventually. When researching the error, I see mention of symlinks as a potential problem. Do you happen to have any symlinks on the test machine? @rumanaHaque |
As shown in the stack trace above - I cannot run using this podman build command since this is a temp Containerfile that is created, and I don't have access to it later on.
|
Hi @cherylking - confirmed I am not using any Symlinks.
|
Here is the temp Containerfile that devc generates when I run the command mvn liberty:devc.
|
I'm attaching a word doc that contains the very long error string parsed out into separate lines. |
Just adding here that this is a Windows only problem, and Matt is working on a PR currently that will probably fix this issue. I will post here when we have a snapshot driver of LMP to try. |
@rumanaHaque The |
@cherylking @mattbsox Here is the stack trace:
I still get a diff error - but that is the application timing out.
But the error for this problem has been fixed in the latest release of the liberty maven plugin. |
I am running TER - https://github.ibm.com/websphere/system-test/issues/906 to test the Liberty Tools using Eclipse in Windows VM.
I imported ACME ee10 application to the worskspace, and I can start and stop the application successfully using the Start and Stop commands from the Liberty Dashboard.
I have podman installed and started in my Windows VM, but when I try to run the "Start in Container" using the Liberty Dashboard, I get the following error.
The text was updated successfully, but these errors were encountered: