Open floriansiepe opened 2 years ago
/cc @DavideD, @Sanne, @gavinking, @mswatosh, @yrodiere
@Sanne does it ring a bell? It looks like some action at the end of the container start is failing?
sorry, no doesn't ring a bell. I just tested it locally and it worked fine; my oracle image was 9533b82f826a13ef97bc9834396b18e0c4f31f0a5c1514ac7e2f6a8f59a5e99f
- but the above error mentions 76be7f6cda7e2762ec8e4ea7641722bb7181042f9d27c93e67de9d3be502bca2
I wonder if there has been a briefly broken image on dockerhub?
I really think we should start using hard-tags
@Sanne Can you then tell me, what is the right image tag to use? E.g. what is the tag behind 9533b82f826a13ef97bc9834396b18e0c4f31f0a5c1514ac7e2f6a8f59a5e99f
?
@Sanne Can you then tell me, what is the right image tag to use? E.g. what is the tag behind
9533b82f826a13ef97bc9834396b18e0c4f31f0a5c1514ac7e2f6a8f59a5e99f
?
Sure, the container we're starting behind the scenes is docker.io/gvenzl/oracle-xe:21-slim-faststart
. I was wondering if you were possibly getting a slightly out of date container image compared than mine, but honestly that's far fetched - just trying to reproduce your exact scenario in all details.
What else can you tell me abour your environment; I infer OSX - using Docker?
Seems similar to https://github.com/oracle/docker-images/issues/1689 - perhaps not a Quarkus specific issue.
I'm using OSX 12.6 on an M1 chip. I already issued the commands described in https://hub.docker.com/r/gvenzl/oracle-xe regarding the M1 chips and restarted the Docker engine. However, without success. In docker desktop I can observe that the container exits (1) immediately. I also pulled a fresh version of the image. I guess it may be a arm64 problem.
Right it would seem to be related to running Oracle on M1.
Could you try the instructions in section "Oracle XE on Apple M chips" on https://hub.docker.com/r/gvenzl/oracle-xe ? They suggest to use colima - but not having a Mac I've never explored this.
Wondering how we can improve things a little on the Quarkus side; at least throwing a meaninfgul error would be nice. cc/ @holly-cummins ?
@Sanne I used colima to emulate x86 architecture. After several restarts of both colima and docker desktop I had no success either.
I'm afraid then that from my side the only thing I can do is to disable the use of devservices/Oracle when on M1.
One way out for you would be to try Testcontainers Cloud ? Our devservices implementation is based on Testcontainers; if you enable their commercial offering, it will transparently start the containers somewhere else and re-route the traffic - so your tests would work.
(and I'm sorry to suggest a commercial solution - I just don't see other options, assuming you can't get colima to work)
I agree, @Sanne, we can probably offer more help in these case. I mean, we do already know it's working, which is why we disable our tests.
I wonder if we can/should do a generic solution for a not-working devcontainers? We know in our builds what tests we've disabled on M1, so we could either
Describe the bug
Oracle Database Dev Service is unable to start database container.
Expected behavior
Database container should start normally
Actual behavior
Log output of
quarkus dev
How to Reproduce?
Steps to reproduce:
quarkus-jdbc-oracle
andquarkus-hibernate-orm-panache
extensionquarkus dev
Output of
uname -a
orver
Darwin A0539W05 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000 arm64
Output of
java -version
openjdk version "17.0.4" 2022-07-19 OpenJDK Runtime Environment GraalVM CE 22.2.0 (build 17.0.4+8-jvmci-22.2-b06) OpenJDK 64-Bit Server VM GraalVM CE 22.2.0 (build 17.0.4+8-jvmci-22.2-b06, mixed mode, sharing)
GraalVM version (if different from Java)
22.2.0
Quarkus version or git rev
2.13.0.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.6
Additional information
No response