-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running quickstart.sh in WSL2 ends with errors #57
Comments
@Ali-MRDN47 in your @fuzziebrain any other thoughts? |
Running The error singled out here:
... is a bug and I'll fix it soon. It shouldn't affect a first build. It will break if the The problem is captured in the build log:
I'd recommend that you perform the following steps:
|
Not too sure if you had sent a reply, but you had this error:
This is an issue with Windows restricting the use of certain ports, likely because you have Hyper-V enabled. |
Yes, I've replayed but I've removed it later because it was irrelevant, sorry. I solved this problem by adjusting the ports |
Hi, I had the same issue when I tried to install apex 22.1 on wsl-2 in docker today. The source of the issue is default user for docker container, you are not root but oracle, in previous installation for version 21.2 few months ago I was root when I called ( docker exec -it xx bash), It seems to be that scripts are not running under root in docker container but under oracle user, for some tasks (I identified only java installation) they are not sufficient priviliges assigned. Ales |
Changing permission on "files" folder before running the quickstart.sh also worked for me. |
Hi there,
I'm trying to run the project on my windows 10 machine using wsl2 with ubuntu distribution.
I'm using wsl2 terminal to run the script quickstart.sh. I've already downloaded and copied
jre-8u321-linux-x64.tar.gz
into the folderfiles
and adjusted thesettings.env
file as follow:I got the following error at the end of the execution after installing a lot of stuffs:
what I can understand is, that Java istn't installed in on the container.
Here are the files:
01-build.log
02-run.log
)
Can anyone tell me, what's the problem is?
The text was updated successfully, but these errors were encountered: