Closed denismaggior8 closed 2 years ago
@denismaggior8 Are you building on an ARM host machine? I tried on an Oracle cloud VM and on my laptop with a standard Oracle JVM, but I am unable to reproduce this error.
Yes, MacBook Pro with M1 processor. The issue seems to be the WebLogic installer, not image-tool itself. I need to build an ARM-native WebLogic image (just for testing purpose) because the x86 one, emulated with qemu, is too slow on my laptop. I'm wondering what's wrong with the installer on M1 processor, the JDK version is among the supported ones... I can help you troubleshoot this issue, do you know what it means "Unable to locate the startup/shiphome directory" ?
@denismaggior8 I am not sure what this is referring to. I have a couple guesses. The easiest first step to debug is to disable Docker buildkit so that we can see the log. If we don't get any information that way, we can alter the Dockerfile to print the installer log.
To disable: export DOCKER_BUILDKIT=0
To modify the Dockerfile, you or I will need to modify src/main/resources/docker-files/install-middleware.mustache on or near line 47 to echo /tmp/OraInstall*/install*.log
@denismaggior8 Can you run the same installer locally on your Mac? It would be much easier to see the log that way versus being in a container.
We do not support WebLogic Server installers on ARM on MacOS
Hi @mriccell, nice to meet you again. We met a couple of years ago at a customer's HQ in Moncalieri (Turin/Italy). I understand you don't support the WebLogic's installer on Apple M1 processors but, since this architecture will be massively adopted by developers using macOs in the next few years, I can offer my support to to start testing it, what do you think?
@ddsharpe thanks for your kind support, I have disabled BuildKit using export DOCKER_BUILDKIT=0
and then re-run
$ imagetool.sh create \
--type wls \
--version 12.2.1.4.0 \
--tag wls:122140 \
--user 123.465@mydomain.com \
--password xyz
The build.log that I got is the one attached to this comment.
Let me know. Denis
@denismaggior8 Can you run the same installer locally on your Mac? It would be much easier to see the log that way versus being in a container.
I've set up this repo for testing purpose, docker build gives me the same "Unable to locate the startup/shiphome directory" error as image tool.
@denismaggior8 posted to your repo in the issues. Awaiting feedback.
@denismaggior8 should we keep this open? I don't see any traffic here or in your repo.
Yes please, I had some busy weeks but since tomorrow I'll be back working on it. I'll update you soon
Hi
facing the same issue , any luck on finding workaround to this ? I am trying to build new 12214 image on arm64 platform using my macOS/dockerDesktop.. the same image I can then upload to my private repo and then reuse it to create my Weblogic domain in 2 nodes-K8S cluster running on Debian VMs on my MACOS also using the ARM64, VMs are running on UTM( kinda virtual box..) the default 12214 image is built on x64 platform and I can't deploy it in my ARM64-K8S cluster, thus the reason for me to create new 12214 image that can be supported and run in ARM64 arch and using docker on macOS
any hints are much appreciated
Hi @hfatnaci, the error seems to be related to a bug that affects the installer when run from an arm64 JDK. I think that @ddsharpe already opened an issue to the dev team, meanwhile you can follow this guide to build your own arm64 WLS image (bypassing the installer) https://github.com/sunnyvale-it/oracle-weblogic-apple-arm64-docker-image
Tell me if it works for you.
@hfatnaci @denismaggior8 This is not an Image Tool issue. The Oracle installer fails on MacOS ARM with or without Docker and the Image Tool involved. I have filed an issue with the Oracle team. If this is an issue for you or your company, please file a "me too" support case with Oracle Support. Filing a support case would help let the support team know how many people this affects, and will help you get notified when a fix is available.
Thanks @denismaggior8 for the prompt reply.. the guide was indeed helpful to build an few 12214 image with arm64 platform ...still need to try to run it in my k8S cluster also running on arm64 arch agree @ddsharpe , when launching the imagetool to create the image, the error is occurring during the installation process of the middleware which is basically a java process against the installer jar.. the workaround on the guide provided by @denismaggior8 is basically copying an existing installation from x86 image to an image built on arm64 with jdk that is also arm64.. I still have to see if that image will work smoothly :) but it seems the actual support of fmw is not entirely there for ARM64, according the matrix support : https://www.oracle.com/technetwork/middleware/fmw-122140-certmatrix-5763476.xlsx the support for 12214 on ARM64 is only on OEL7, so in theory the imagetool should also support this and able to build an image of 12214 on OEL7 on ARM64 arch.. the image can be then executed on docker on macOS or a Linux VM on macOS and that should be still supported by oracle.. as we are not trying to run/install fmw12214 on a bare macOS which we know isn't supported
Oracle JDK and FMW teams are working on support for MacOS ARM. For now, Image Tool will have to wait.
My setup
Image tool version
Docker version
macOS version
Apple platform
How to reproduce
Add the WLS binary into the cache
Add the JDK binary into the cache
Create the image
Relevant errors:
The comple log can be found here:
imagetool.log
@mriccell @markxnelson please advise