Common Issues

Version 24.0.12 and older

Issue	Workaround
You want to use the Start action in the Liberty dashboard to start Liberty dev mode without any parameters after you previously used the Start… action to bring up the run configuration editor and add additional parameters. However, if you previously edited the run configuration, the next time you start Liberty dev mode using the Start action, the same parameters are added to the run configuration.	The Start action actually just starts Liberty using whatever parameters are specified in the currently selected run configuration. The Start… action is a shortcut to edit the configuration before launching. To start Liberty without any parameters after you previously added parameters, you must either edit the current run configuration or create a new configuration.
When you start Liberty in a container, it might fail with the message “<Container> : Error response from daemon: unable to find user : no matching entries in passwd file.”	Use the latest version of the liberty-maven-plugin or liberty-gradle-plugin in the pom.xml or build.gradle file.
You might encounter issues with the maven-surefire-report-plugin version 3.5.0. These include a PluginExecutionException and a RuntimeException, which can lead to test report generation failures for both unit tests and integration tests in a Liberty Maven project.	If you encounter this problem, clear the relevant Maven cache by deleting all the files and folders in the directory that contains the surefire folder located at <user-home>/.m2/repository/org/apache/maven/. Afterward, Liberty Tools will automatically download the latest Maven Surefire Plugin version the next time your project’s tests are run through Liberty dev mode. This should resolve the issue. Ensure that you do not specify version 3.5.0 of either maven-surefire-plugin or maven-surefire-report-plugin in your project’s pom.xml.