Open Ali-MRDN47 opened 2 years ago
@Ali-MRDN47 in your settings.env
file can you remove the reference to FILES_DIR=files
(first line) and try again?
@fuzziebrain any other thoughts?
Running ./quickstart.sh
shouldn't have required creating a different .env
file, it would have been created for you.
The error singled out here:
##### Install dependencies if required #####
tar (child): /tmp/files/java17: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
tar (child): /tmp/files/java17: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
... is a bug and I'll fix it soon. It shouldn't affect a first build. It will break if the <CONTAINER_NAME>-oradata
directory exists from a previous deployment.
The problem is captured in the build log:
##### Install dependencies if required #####
Loaded plugins: ovl
ovl: Error while doing RPMdb copy-up:
[Errno 13] Permission denied: '/var/lib/rpm/Dirnames'
You need to be root to perform this command.
I'd recommend that you perform the following steps:
docker rm -vf <CONTAINER_NAME>
. <CONTAINER_NAME>-oradata
directory using the command sudo rm -rf <CONTAINER_NAME>-oradata
.sudo -K
../quickstart.sh
@Ali-MRDN47
Not too sure if you had sent a reply, but you had this error:
docker: Error response from daemon: Ports are not available: listen tcp 0.0.0.0:55500: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
This is an issue with Windows restricting the use of certain ports, likely because you have Hyper-V enabled.
@Ali-MRDN47
Not too sure if you had sent a reply, but you had this error:
docker: Error response from daemon: Ports are not available: listen tcp 0.0.0.0:55500: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
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. I solved (as workaround) the issue by adding su -c commnand for installing of java in scripts, now env seems to be working (workspace & test app created).
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?