You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a websphere-liberty Docker container (docker run --name wlp -P -td websphere-liberty)
In Eclipse, create a new Liberty server for the Docker container, make sure that the 'Run applications directly from the workspace' checkbox is checked
Add a web application to the server and make sure it runs
Switch the server to non-loose config mode
The application war does not get published and the loose configuration file is still in the apps directory, if you try to run it, it will fail
Also, if you try to change the server.xml file in Eclipse this will fail as well with the following message:
Failed to synchronize server configuration. Check the server logs for details.
The remote server configuration synchronization failed. Verify the remote configuration directories exist and the server is configured with the correct write permissions to those directories. See the workspace log and remote server logs for additional details.
On MAC it is slightly different. When switching to non-loose config mode it get stuck in starting state because the container exits with the following in the logs:
cp: failed to access '/config/configDropins/defaults/keystore.xml': Permission deniedCWWKE0005E: The runtime environment could not be launched.
CWWKE0010E: The required server.xml file must exist and be readable. Path: /opt/ibm/wlp/usr/servers/defaultServer/server.xml Reason: file not found
Command: /opt/ibm/java/jre/bin/java
Java home: /opt/ibm/java/jre
Install root: /opt/ibm/wlp/
System libraries: /opt/ibm/wlp/lib/
User root: /opt/ibm/wlp/usr/
Config: /opt/ibm/wlp/usr/servers/defaultServer/
Output: /opt/ibm/wlp/output/defaultServer/
It is likely the same problem though where some of the files are owned by root and not accessible by the 'default' user.
The text was updated successfully, but these errors were encountered:
To reproduce on Windows:
Failed to synchronize server configuration. Check the server logs for details.
The remote server configuration synchronization failed. Verify the remote configuration directories exist and the server is configured with the correct write permissions to those directories. See the workspace log and remote server logs for additional details.
On MAC it is slightly different. When switching to non-loose config mode it get stuck in starting state because the container exits with the following in the logs:
It is likely the same problem though where some of the files are owned by root and not accessible by the 'default' user.
The text was updated successfully, but these errors were encountered: