In version 3.8.1, encountering an error in 'Start in container' functionality while running in Podman and Docker

[vaisakhkannan]

When we run 'Start in container' using podman (v 4.9.3) we are getting the following error.

Starting container...

Container command: docker 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 /root/Documents/DEVEX/intellij/test-24.0.3/app-name-gradle-parent/app-name-gradle-new/build/.libertyDevc/apps:/config/apps -v /root/Documents/DEVEX/intellij/test-24.0.3/app-name-gradle-parent/app-name-gradle-new/build/.libertyDevc/dropins:/config/dropins -v /root/Documents/DEVEX/intellij/test-24.0.3/app-name-gradle-parent/app-name-gradle-new:/devmode -v /root/Documents/DEVEX/intellij/test-24.0.3/app-name-gradle-parent/app-name-gradle-new/build/wlp/usr/servers/defaultServer/logs:/logs -v /root/.m2/repository:/devmode-maven-cache --user 0 --name liberty-dev app-name-gradle-new-dev-mode server debug defaultServer -- --io.openliberty.tools.projectRoot=/devmode

docker: Error response from daemon: unable to find user 0 : no matching entries in passwd file.

An error occurred while running the container: docker: Error response from daemon: unable to find user 0 : no matching entries in passwd file. RC=125

> Task :libertyDevc FAILED

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ':libertyDevc'.

> io.openliberty.tools.common.plugins.util.PluginExecutionException: An error occurred while running the container: docker: Error response from daemon: unable to find user 0 : no matching entries in passwd file. RC=125

If we change the 'liberty-gradle-plugin' to previous version (3.8) start in container is working without any issue.

[cherylking]

@vaisakhkannan Thank you for reporting this. We discovered this issue last week and have produced a fix. Please try the latest release 3.8.2 (published earlier this week - release notes do not exist yet). If that does not fix the issue, please reopen. Thanks.

The fix is in our common dependency used by both our Maven and Gradle plugin.