mirror of
https://github.com/dbeaver/cloudbeaver.git
synced 2026-04-25 05:36:14 +03:00
[GH-ISSUE #1141] Docker image creates files as root in mounted directory #242
Labels
No labels
AS
can't reproduce
can't reproduce
deployment
development
documentation
duplicate
duplicate
ee
enhancement
external
new driver
performance
pull-request
third party issue
wait for response
wait for review
wontfix
x:Oracle
x:cassandra
x:clickhouse
x:db2
x:duckdb
x:greenplum
x:h2
x:h2gis
x:hana
x:hive
x:intersystems
x:kyuubi
x:maria
x:mongo
x:mysql
x:postgresql
x:presto
x:sql server
x:sqlite
x:teradata
x:trino
xf:accessibility
xf:administration
xf:ai
xf:authentication
xf:aws
xf:commit-mode
xf:connection
xf:dark theme
xf:data editor
xf:datatransfer
xf:dba
xf:driver management
xf:erd
xf:filters
xf:i18n
xf:i18n
xf:installer
xf:json
xf:kerberos
xf:ldap
xf:local config
xf:log viewer
xf:metadata
xf:metadata editor
xf:navigator
xf:okta
xf:query manager
xf:resource manager
xf:scripts
xf:sql editor
xf:tasks
xf:ui/uix
xo: Firefox
xo:eclipse
xo:internet explorer
xo:macos
xp:major
xrn:internal
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cloudbeaver#242
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mjarosie on GitHub (Sep 10, 2022).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/1141
Describe the bug
Docker image creates files as root in mounted directory. That prevents me from modifying the content of the default configuration after it's created by the container (as my IDE is running as non-root).
To Reproduce
The output of
ls -al workspacenow is:Desktop (please complete the following information):
Additional context
When I try running the container as a non-root user (i.e. uncomment
# userline indocker-compose.yamlfile) - the application fails to start with the following error:An obvious workaround is to
chownfiles that I'd like to modify in my IDE. I'm wondering if there's any easier way to make it work (e.g. make the container run as a non-root user).@kseniaguzeeva commented on GitHub (Sep 14, 2022):
Thank you for the report. We are going to fix this issue. To do this, we need to investigate it in order to find the best solution of this problem.
@mayerro commented on GitHub (Dec 16, 2022):
@mjarosie
before container starts you must build your own image with an user inside.
Create Dockerfile which contains:
In next step change your compose file:
Search additional information about build here
Now you can run compose
@kseniaguzeeva commented on GitHub (Jan 9, 2023):
I close the ticket, because I don't see any updates for a long time. If you have any questions, feel free to contact me to reopen the ticket.