-
Notifications
You must be signed in to change notification settings - Fork 90
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
In version 3.10.1, encountering an error in 'Start in container' functionality while running in Podman. #1807
Comments
@aparnamichael This is a duplicate of issue 1802 and is fixed in version 3.10.2 of our plugin. That version was just published earlier this week and the release notes have not been created yet. If version 3.10.2 does not resolve this issue, please reopen. |
@cherylking The |
@aparnamichael Is the error identical using 3.10.2 on Linux? Can you please include the logging output that shows the podman commands that were run when using version 3.10.2? |
I apologize, @cherylking . After uninstalling and reinstalling Podman and attempting to run "start in container" again with both maven versions 3.10 and 3.10.2, everything seems to be working fine. Therefore, I am closing the issue for now. |
@aparnamichael Oh good! I was confused why the fix would not have worked for you, as I had someone test it on Linux specifically. |
When we run 'Start in container' using podman (v 4.9.3) we are getting the following error.
[INFO] Starting container...
[INFO] Container command: podman run --rm -p 9080:9080 -p 9443:9443 -p 7777:7777 -e WLP_DEBUG_SUSPEND=n -e WLP_DEBUG_ADDRESS=7777 -e WLP_DEBUG_REMOTE=y -v /Users/aparnacmichael/Documents/Test-24.0.3/Intellij/app-name-intellij-one/target/.libertyDevc/apps:/config/apps -v /Users/aparnacmichael/Documents/Test-24.0.3/Intellij/app-name-intellij-one/target/.libertyDevc/dropins:/config/dropins -v /Users/aparnacmichael/Documents/Test-24.0.3/Intellij/app-name-intellij-one:/devmode -v /Users/aparnacmichael/Documents/Test-24.0.3/Intellij/app-name-intellij-one/target/liberty/wlp/usr/servers/defaultServer/logs:/logs -v /Users/aparnacmichael/.m2/repository:/devmode-maven-cache --user 501 --name liberty-dev app-name-intellij-one-dev-mode server debug defaultServer -- --io.openliberty.tools.projectRoot=/devmode
[ERROR] Error: preparing container b6f0b079bed6815152e908f06a9a7297086935163efeeda0b4eb72231a6b1a15 for attach: unable to find user 501 : no matching entries in passwd file
[ERROR] An error occurred while running the container: Error: preparing container b6f0b079bed6815152e908f06a9a7297086935163efeeda0b4eb72231a6b1a15 for attach: unable to find user 501 : no matching entries in passwd file RC=126
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:05 min
[INFO] Finished at: 2024-03-13T16:22:16+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.10.1:devc (default-cli) on project app-name-intellij-one: Error starting the server in dev mode.: An error occurred while running the container: Error: preparing container b6f0b079bed6815152e908f06a9a7297086935163efeeda0b4eb72231a6b1a15 for attach: unable to find user 501 : no matching entries in passwd file RC=126 -> [Help 1]
If we change the 'liberty-maven-plugin' to previous version (3.10) start in container is working without any issue.
The text was updated successfully, but these errors were encountered: