-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Encoding issue when upgrading to Quarkus 3 using Dockerfile.native-micro #40027
Comments
You can try to set the file encoding in native explicitly via
|
When building the native image, you can include the following properties in your
|
I'm going to test your suggestion. However, I'm not sure if it will work. In the logs, you can see that I thought that the fix was going to be in the lines of making Will update the issue shortly with the results. |
Update: It didn't work |
For the sake of testing, also I tried setting the language ENVs to UTF-8 in the Dockerfile, without success
FROM quay.io/quarkus/quarkus-micro-image:2.0
ENV LANGUAGE='en_US:en'
ENV LANG='C.UTF-8'
ENV LC_ALL='C.UTF-8'
WORKDIR /work/
RUN chown 1001 /work \
&& chmod "g+rwX" /work \
&& chown 1001:root /work
COPY --chown=1001:root target/*-runner /work/application
EXPOSE 8080
USER 1001
ENTRYPOINT ["./application", "-Dquarkus.http.host=0.0.0.0"]
|
@gian1200 Have you tried the latest Quarkus version? Today that is 3.9.3. If the issue still persists, can you be more specific on the reproducer? I did the following and it all looks fine with the Quarkus getting-started-reactive:
$ ./mvnw package -Dnative -Dquarkus.native.container-build
$ podman build -f src/main/docker/Dockerfile.native-micro -t quarkus/getting-started-reactive .
$ podman run -i --rm -p 8080:8080 quarkus/getting-started-reactive
|
Thanks for answering, @galderz. I'll try to update it and retry. The only difference I see from your reproducer is that we use |
A couple of hours ago oracle/graal#8792 was reported which seems/could be related. |
What issues are you having in your CI env? Underneath |
No need to worry about it. It's an issue specific to our CI env. We don't have docker or podman available inside the containers where our pipelines are running.
Yeah, I was actually doing that (still WIP). I will also try with I will post an update in a few days. |
Quick update: confirmed. It worked with ol7. This means this is affected by oracle/graal#8792 |
Since the issue is in Graal and not Quarkus, I'm proceeding to close the issue. PS: I didn't test it with |
Describe the bug
When upgrading to Quarkus 3.7.3 from Quarkus 2 (2.16.12.Final), logs started having problems printing some chars (áéíóú). This happened when running in a Kubernetes server.
Dockerfile.native-micro
doesn't seem to be defaulting to UTF-8. Is this expected?Output on remote running pod (
Dockerfile.native-micro
):Expected behavior
At least chars with accent (áéíóú) should correctly appear in logs
Actual behavior
Chars with accent (áéíóú) appear as "?" in the log
How to Reproduce?
Image used to build:
ghcr.io/graalvm/graalvm-ce:ol8-java17-22
Steps to build:
Output of
uname -a
orver
No response
Output of
java -version
17.0.8+7-jvmci-22.3-b22
Mandrel or GraalVM version (if different from Java)
GraalVM 22.3.3 Java 17 CE
Quarkus version or git rev
3.7.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.6
Additional information
Same image/steps to build worked fine with Quarkus 2
Maybe some related issues:
#11222
quarkusio/quarkus-images#86
Fragment build log:
The text was updated successfully, but these errors were encountered: