-
Notifications
You must be signed in to change notification settings - Fork 16
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
Jbang-catalog can't be downloaded #49
Comments
What are you doing exactly to get this error? Thanks. |
I think the error comes from these lines :
But if you want some more context, I can share the complete Dockerfile with you. |
OK, I wanted to know if it was a problem with Quarkus CLI. Apparently it's a problem with either JBang or the GitHub infra. /cc @maxandersen |
With the docker-compose up --build, we still got these logs :
Where we can find our 2 last lines (steps 4 and 5) |
can you run with |
I tried to add |
ah, try with "-e" or "--errors" then CLI should print info. |
Nothing I add to the line in Dockerfile seems to change the error log I got. |
Hello, I work on the same team as @Bullfrog666 As you can see none of the arguments seem to do anything :/ Can jbang triggers its verbose mode based on ENV var ? |
Do you have the failing docker file or somehow provide reproducer? Does it happen locally too? |
@iocanel didbt you recently fix something around not having the cli fail when it cannot download the metadata? |
our complete dockerfile: FROM openjdk:17-ea-slim-buster
RUN apt update
RUN apt install -y curl wget
RUN curl -Ls https://sh.jbang.dev | bash -s - trust add https://repo1.maven.org/maven2/io/quarkus/quarkus-cli/
RUN curl -Ls https://sh.jbang.dev | bash -s - app install --fresh --force quarkus@quarkusio
ENV PATH="${PATH}:/root/.jbang/bin"
RUN mkdir -p /opt
RUN wget -q https://dlcdn.apache.org/maven/maven-3/3.9.4/binaries/apache-maven-3.9.4-bin.tar.gz -O /opt/apache-maven.tar.gz
RUN cd /opt && tar xf /opt/apache-maven.tar.gz
ENV PATH="${PATH}:/opt/apache-maven-3.9.4/bin"
WORKDIR /deployments/quarkus
COPY ./backend/pom.xml ./pom.xml
RUN mvn dependency:resolve
# previously CMD [ "quarkus", "dev" ]
CMD [ "sleep", "infinity" ] it works locally for @Bullfrog666 and the other dev who also do backend |
The fix was merged 2 weeks ago and was specific to cli plug commands. If there are other areas of the cli that reach for the jbang catalog they might not be covered. |
so you you build that dockerfile, then do @iocanel any idea why |
can you show the log that happens before that line? @Bullfrog666 says it happens when installing quarkus cli but @vic1707 writes as it fails when running quarkus dev. those two are quite different so would be good to know exactly which scenario we are talking here. In any cases if it works from some but fails for others I'm assuming it is some network setup differences. maybe one is running in a container that are not allowed to access github.com wiothut a proxy configuration or similar? |
I talked with Bullfrog to clarify everything. the jbang error happens when running any Locally the I just went back the a few commits of our dockerfile and one of the last changes was - FROM eclipse-temurin:17-jdk
+ FROM openjdk:17-ea-slim-buster which once reverted seems to fix the |
there could be some certificate issues/differences? if you have a container that fails to execute quarkus commands - can you run curious to grok why temurin images are giving you a hard time but maybe that's a different issue. |
here's the output
|
damn - sorry i missed it was quarkusio it had issues with. can you try |
you can also try run:
and you can also do "vi |
Sorry couldn't do it yesterday. Bingo you were right !
As for the edition of quarkus
|
Sorry i missed the Update. The error is Weird. Do You have it accessing a read only dir somehow ? Like. This shouldnt happen. Where can You reproduce it ? Did You find a way around it ? |
Any chance you are having concurrent executions of jbang on the same filesystem? I could possibly see a race condition here but I'm not fully convinced so really wanna be able to reproduce this. |
Hello, no problem. We found a way around it by calling I doubt there was concurrent executions of I tried to reproduce it in a standalone container without success. |
Since the last update (3.4.2) we've been having an error when building our docker, which launches a back in quarkus :
The text was updated successfully, but these errors were encountered: