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
Copy file name to clipboardExpand all lines: documentation/staging/content/navigate/image.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,7 +115,8 @@ latest capabilities, many of which are exposed by this application. As such, us
115
115
recommended.
116
116
117
117
{{% notice note %}} For "Model in Image" or "Domain in Image" [domain locations]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}),
118
-
when building your primary or auxiliary image, we highly recommend using WDT 2.0 to take advantage of enhanced capabilities that reduce the chance of deploy-time errors created due to a bad model.
118
+
when building your primary or auxiliary image, Oracle strongly recommends using [WDT 2.0](https://github.com/oracle/weblogic-deploy-tooling/releases).
119
+
Certain WKT UI actions, such as `Prepare Model`, may rewrite the model into a format that earlier WDT versions cannot parse.
Copy file name to clipboardExpand all lines: documentation/staging/content/release notes/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,15 @@ pre = "<b> </b>"
9
9
10
10
- For "Model in Image" domains, added the ability to configure, push, and use an auxiliary image.
11
11
- Added these actions:
12
+
- Validate WDT model files
13
+
- Create and push an auxiliary image
12
14
- Update and uninstall the WebLogic Kubernetes Operator
13
-
- Uninstall the ingress controller
14
15
- Undeploy the WebLogic domain
16
+
- Uninstall the ingress controller
15
17
16
18
### Known Issues
17
19
18
-
- When running the WKT UI application on Windows, the image builder tool (docker or podman) also must be directly executable in Windows. For example, there is currently no support for running the WKT UI application in Windows and running podman under the Windows Subsystem for Linux (WSL2). However, running Docker Desktop for Windows with a WSL2 backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call WSL2). If you need to use podman on Windows, then refer to the podman blog entries at https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html for more information about downloading, installing, and configuring the Windows Remote Client.
20
+
- When running the WKT UI application on Windows, the image builder tool (Docker or Podman) also must be directly executable in Windows. For example, there is currently no support for running the WKT UI application in Windows and running Podman under the Windows Subsystem for Linux (WSL2). However, running Docker Desktop for Windows with a WSL2 backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call WSL2). If you need to use Podman on Windows, then refer to the Podman blog entries at https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html for more information about downloading, installing, and configuring the Windows Remote Client.
19
21
20
22
- On Linux, the application depends on libGL being installed. libGL is not currently listed in the dependencies list for the `rpm` (or `deb`) installers. Therefore, you will need to install libGL using your package manager. For example:
21
23
```
@@ -25,5 +27,3 @@ pre = "<b> </b>"
25
27
- When trying to run the application on a Linux machine and display it on a Windows machine, do not use the Xming X server. There appears to be a bug (presumably with their OpenGL support) that prevents applications using Electron 13.x or later from working (for example, Microsoft VS Code doesn't work either).
26
28
27
29
- The application is limited to working with archive files whose size is less than 2 GB.
28
-
29
-
- On MacOS, after editing a model in the Model Code View's model editor pane, you must click outside the editor pane prior to using the Menu to save or perform other actions that need the latest model content. This is due to Electron bug [31915](https://github.com/electron/electron/issues/31915) that fails to generate the proper events when the Menu is selected on MacOS.
Copy file name to clipboardExpand all lines: documentation/staging/content/setup/install.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Alternatively, you can download the `AppImage` file, copy it to your local file
28
28
29
29
- Use your file manager, right click on the file, edit the properties, and change the permissions to make it executable.
30
30
31
-
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.
31
+
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.
32
32
33
33
#### Helpful Hints
34
34
@@ -66,7 +66,7 @@ Upon application startup, if a more recent version exists, an Application Update
66
66
- `Install Now`
67
67
- `Install on Exit`
68
68
- Downloads the application and installs it after you exit.
69
-
- Not available on MacOS.
69
+
- Not available on macOS.
70
70
- `Ignore Update`
71
71
72
72
At any time, you can check for application updates using `Help > Check for WKT UI Updates`.
0 commit comments