Each release has many assets, some of which are needed for the application’s auto-update functionality and are not intended to be used for installing the application. The following table lists the installer file names and their purpose.
|Installer File Name||Purpose|
|WebLogic-Kubernetes-Toolkit-UI-1.4.1-arm64.dmg||macOS Apple Silicon (M1) installer.|
|WebLogic-Kubernetes-Toolkit-UI-1.4.1.AppImage||Linux AppImage package of the application.|
|WebLogic-Kubernetes-Toolkit-UI-1.4.1.dmg||macOS Intel (x86-64) installer.|
|wktui-1.4.1.x86_64.rpm||Linux RPM package installer.|
|wktui_1.4.1_amd64.deb||Linux DEB package installer.|
The Linux AppImage package is not an installer. It is a portable packaging of the application that can run directly without installation on a compatible Linux machine. For more information, see https://appimage.org/.
NOTE: On Linux, to get all the dependencies and have them installed in the correct order, you need to use the package manager to install the
deb file. First, be sure to review the Linux prerequisites here.
For RPM-based systems, use either
dnf; for example:
yum update sudo yum -y localinstall wktui_1.0.0_amd64.rpm
For Debian-based systems, use:
sudo apt update sudo apt upgrade sudo apt install ./wktui_1.0.0_amd64.deb
If the installation is on a server machine, you should
logout from the current terminal session and use X11 forwarding mechanism or any remote desktop application to the remote terminal for launching the WKT UI application.
Alternatively, you can download the
AppImage file, copy it to your local file system, then either:
Open a terminal, navigate to the directory where the file exists, and make it executable; for example:
chmod u+x <AppImage Name>
Use your file manager, right click on the file, edit the properties, and change the permissions to make it executable.
If you download and run the
AppImage file, you get the added benefits of 1.) Not requiring an installation or root access and 2.) Being able to participate in the auto-update functionality, like macOS and Windows.
When launching the WKT UI application, if you see this:
libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
This is harmless and can be removed by setting the environment variable:
If you are storing credentials in the OS native store, and you see this failure message:
Error occurred in handler for 'save-project': Error: Failed to save credential for image. imageRegistryPushUser: Error: No such interface "org.freedesktop.Secret.Collection" on object at path / org/freedesktop/secrets/collection/login at /tmp/.mount_WebLogpIPFto/resources/app.asar/app/js/credentialManager.js:92:32
You can solve it by running this command (only once) before launching the WKT UI application:
dbus-update-activation-environment --systemd DBUS_SESSION_BUS_ADDRESS DISPLAY XAUTHORITY
Application startup detects Internet connectivity to GitHub. If it fails to connect, a
Network Configuration dialog appears in which you can set or modify your proxy settings, test your changes, and then restart the application.
Launching the application displays a thorough “Introduction” to the WKT UI. Step through it or dismiss it; you can peruse it at any time using
Help > Show Introduction.
Upon application startup, if a more recent version exists, an Application Update dialog appears with these choices:
Install on Exit
At any time, you can check for application updates using
Help > Check for WKT UI Updates.
For updates to in-application versions of WKT Tools (WebLogic Deploy Tooling and WebLogic Image Tool), select
Help > Check for WKT Tool Updates.