From bf5418d25c3fc0fbdc921e362ebf58931bc5c00b Mon Sep 17 00:00:00 2001 From: vsevel Date: Thu, 6 Jun 2024 14:02:37 +0200 Subject: [PATCH] Remote Development Mode docker permissions (cherry picked from commit 5224f69f58453433cb911be41ab68127bc37b910) --- docs/src/main/asciidoc/gradle-tooling.adoc | 2 +- docs/src/main/asciidoc/maven-tooling.adoc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/main/asciidoc/gradle-tooling.adoc b/docs/src/main/asciidoc/gradle-tooling.adoc index 7871b6a2729e7..85f1531b3ca8b 100644 --- a/docs/src/main/asciidoc/gradle-tooling.adoc +++ b/docs/src/main/asciidoc/gradle-tooling.adoc @@ -294,7 +294,7 @@ Before you start Quarkus on the remote host set the environment variable `QUARKU on bare metal you can set it via the `export QUARKUS_LAUNCH_DEVMODE=true` command and then run the application with the proper `java -jar ...` command to run the application. If you plan on running the application via Docker, then you'll need to add `-e QUARKUS_LAUNCH_DEVMODE=true` to the `docker run` command. -When the application starts you should now see the following line in the logs: `Profile dev activated. Live Coding activated`. +When the application starts you should now see the following line in the logs: `Profile dev activated. Live Coding activated`. You will also need to give the application the rights to update the deployment resources by adding `RUN chmod o+rw -R /deployments` after the `COPY` commands into your Dockerfile. For security reasons, this option should not be added to the production Dockerfile. NOTE: The remote side does not need to include Maven or any other development tools. The normal `fast-jar` Dockerfile diff --git a/docs/src/main/asciidoc/maven-tooling.adoc b/docs/src/main/asciidoc/maven-tooling.adoc index bc6eb6b1d822c..4ba1cf36781d2 100644 --- a/docs/src/main/asciidoc/maven-tooling.adoc +++ b/docs/src/main/asciidoc/maven-tooling.adoc @@ -238,8 +238,8 @@ include::{includes}/devtools/build.adoc[] Before you start Quarkus on the remote host set the environment variable `QUARKUS_LAUNCH_DEVMODE=true`. If you are on bare metal you can set it via the `export QUARKUS_LAUNCH_DEVMODE=true` command and then run the application with the proper `java -jar ...` command to run the application. -If you plan on running the application via Docker, then you'll need to add `-e QUARKUS_LAUNCH_DEVMODE=true` to the `docker run` command. -When the application starts you should now see the following line in the logs: `Profile dev activated. Live Coding activated`. +If you plan on running the application via Docker, then you'll need to add `-e QUARKUS_LAUNCH_DEVMODE=true` to the `docker run` command. +When the application starts you should now see the following line in the logs: `Profile dev activated. Live Coding activated`. You will also need to give the application the rights to update the deployment resources by adding `RUN chmod o+rw -R /deployments` after the `COPY` commands into your Dockerfile. For security reasons, this option should not be added to the production Dockerfile. NOTE: The remote side does not need to include Maven or any other development tools. The normal `fast-jar` Dockerfile that is generated with a new Quarkus application is all you need. If you are using bare metal launch the Quarkus runner