-
Notifications
You must be signed in to change notification settings - Fork 17
Closed
Labels
closed-duplicateClosed in favor of an existing reportClosed in favor of an existing report
Description
Inside of /usr/lib the dart directory stands alone as only being accessible by root:
:/usr/lib$ ls -la
total 64
drwxr-xr-x 1 root root 4096 Jun 3 14:26 .
drwxr-xr-x 1 root root 4096 May 11 00:00 ..
drwxr-xr-x 5 root root 4096 May 11 00:00 apt
drwx------ 5 root root 4096 May 21 11:03 dart
drwxr-xr-x 3 root root 4096 Dec 7 2020 dpkg
drwxr-xr-x 3 root root 4096 Apr 6 2019 gcc
drwxr-xr-x 3 root root 4096 Jun 3 14:26 git-core
drwxr-xr-x 3 root root 4096 May 1 2019 locale
drwxr-xr-x 1 root root 4096 Apr 23 2019 mime
drwxr-xr-x 2 root root 4096 Jun 3 14:26 openssh
-rw-r--r-- 1 root root 261 Mar 19 23:44 os-release
drwxr-xr-x 2 root root 4096 Dec 19 2019 sasl2
drwxr-xr-x 3 root root 4096 Jun 3 14:26 ssl
drwxr-xr-x 3 root root 4096 Jun 3 14:26 systemd
drwxr-xr-x 2 root root 4096 May 11 00:00 tmpfiles.d
drwxr-xr-x 1 root root 4096 Jun 3 14:26 x86_64-linux-gnuThis means that any containers built to use a non root user need a workaround in the Dockerfile like:
RUN chmod -R 755 /usr/lib/dart/In the case where I tripped across this I'm not doing a two stage build to create and copy an AOT binary because I need dart run --observe to profile memory usage.
vishr
Metadata
Metadata
Assignees
Labels
closed-duplicateClosed in favor of an existing reportClosed in favor of an existing report