Closed andytael closed 1 month ago
If the timeout can be increased it might solve the problem. Even better make the timeout a parameter?
Upgrade to version 1.20.1
, unfortunately no difference
Running the test outside of IntelliJ the log file looks like this: logfile.txt
Hi, @andytael this is similar to #7621. Please check this comment
@eddumelendez Oracle-XE is not the same thing. This is the current version, XE is old :-)
I can run Oracle Database 23ai Free on my M1 Mac just fine using colima
Please reopen the issue, it is a blocker currently
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/atael/.colima/default/docker.sock
INFO[0001] cpu: 6
INFO[0001] mem: 8GiB
INFO[0001] disk: 60GiB```
`docker run -d -p 1521:1521 -e ORACLE_PASSWORD=Welcome12345 gvenzl/oracle-free:slim`
From the DB log;
######################### DATABASE IS READY TO USE! #########################
#################################################################### CONTAINER: The following output is now from the alert_FREE.log file: ####################################################################
=========================================================== (3):--ATTENTION-- (3):PARALLEL_MAX_SERVERS (with value 1) is insufficient. This may affect transaction recovery performance. Modify PARALLEL_MAX_SERVERS parameter to a value > 4 (= parallel servers count computed from parameter FAST_START_PARALLEL_ROLLBACK) in PDB ID 3 FREEPDB1(3):Autotune of undo retention is turned on. 2024-08-05T20:39:48.249510+00:00 FREEPDB1(3):Opening pdb with Resource Manager plan: DEFAULT_PLAN 2024-08-05T20:39:49.945362+00:00 Completed: Pluggable database FREEPDB1 opened read write Completed: ALTER DATABASE OPEN
Have you tried the following config? There is no even need to disable ryuk.
Unset the var:
env | grep TESTCONTAINERS_RYUK_DISABLED
TESTCONTAINERS_RYUK_DISABLED=
Tried again and gives this:
15:46:33.174 [testcontainers-ryuk] WARN org.testcontainers.utility.RyukResourceReaper -- Can not connect to Ryuk at localhost:32780
java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:542)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:592)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
at org.testcontainers.utility.RyukResourceReaper.lambda$null$1(RyukResourceReaper.java:105)
at org.rnorth.ducttape.ratelimits.RateLimiter.doWhenReady(RateLimiter.java:27)
at org.testcontainers.utility.RyukResourceReaper.lambda$maybeStart$2(RyukResourceReaper.java:101)
at java.base/java.lang.Thread.run(Thread.java:1583)```
Unfortunately no difference, still get timeout error.
You can do something like this and override the default startupTimeout
OracleContainer oracle = new OracleContainer(ORACLE_DOCKER_IMAGE_NAME)
.withStartupTimeout(Duration.ofMinutes(2))
This should fix your issue.
Yes it did. Thank you!
Module
Oracle Free
Testcontainers version
1.20.0
Using the latest Testcontainers version?
Yes
Host OS
Mac OS Sonoma 14.5
Host Arch
ARM (M1)
Docker version
What happened?
When using the
oracle-free
testcontainer module in a Spring Boot 3.2.7 applcation the tests fails with the following error:By looking the source code there seems to be a hardcoded time for 60 seconds
private static final int DEFAULT_STARTUP_TIMEOUT_SECONDS = 60;
and startup time is Time elapsed: 63.39 sRelevant log output
Additional Information
Colima is used and is started like this:
colima start --arch x86_64 --memory 8 --vm-type=vz --mount-type virtiofs --network-address
the following ENV vars are set: