run with quarkus user (read-write access)

[haraldatbmw]

In OpenShift it is not allowed to run the image with the root user. Therefor OpenShift creates a read-only user. The JTA implementation used by Quarkus needs write access (see #2702). So an exception is thrown if running without a custom user.

To overcome this problem I created a quarkus user with read and write access to the /deployments directory.

[geoand]

Thanks for this @haraldatbmw!

It looks good to me, @cescoffier WDYT?

[cescoffier]

2 questions:

• what about using 1001 as user?
• should we do the same for the native docker file?

[haraldatbmw]

2 questions:

• what about using 1001 as user?

I changed it to 1001. The OpenShift documentation recommends this too.

• should we do the same for the native docker file?

Maybe, this depends on the base docker image of the native docker file.
This is a different one to the jvm base image. I have not tried the native image.

[aloubyansky]

@cescoffier do we want to clarify whether the native image one needs the same before merging this or check later?