-
Notifications
You must be signed in to change notification settings - Fork 9
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
The launch.sh script and underlying container does not work if running as root on the host #181
Comments
We should add |
Different container runtimes in play apply different host mounting strategies which may keep
Although this addresses some of the potential issues with the host permissions, it raises other issues in the current cli-tools images because those have a /home/devops $ ls -al
total 40
drwxr-xr-x 1 devops root 4096 Jul 12 16:08 .
drwxr-xr-x 1 root root 4096 Jun 30 17:21 ..
-rw-r--r-- 1 devops root 833 Jun 30 17:21 .bashrc-ni
drwx------ 4 devops root 4096 Jun 30 17:21 .bluemix
-rw-r--r-- 1 devops root 53 Jun 30 17:16 .terraformrc
drwxr-xr-x 2 devops root 4096 Jun 30 17:16 etc
-rwxr-xr-x 1 devops root 833 Jun 30 17:16 image-message
drwxr-xr-x 1 501 dialout 128 Jul 12 16:07 src
drwxr-xr-x 2 devops root 4096 Jun 30 17:16 terraform
/home/devops $ id
uid=501 gid=0(root) |
With podman on MacOS - host mounts that show as
The host mount UID matches what is specified with
the same error appears with a simple Edit - It appears that even running the
This appears to being caused by an environment variable |
This commit: cloud-native-toolkit/image-cli-tools@c9e799a fixes the environment variable causing issues with podman rootful and colima container engines. It just hasn't propagated to the image referenced in the |
On MacOS when using what appears to be the latest container image with fixes to If the container is running as the host user by ...
╷
│ Error: Failed to install provider
│
│ Error while installing hashicorp/null v3.1.1: mkdir /home/devops/.terraform.d: permission denied
╵
...
This is happening because the user from RUN chmod -R g=u /home/devops
|
No description provided.
The text was updated successfully, but these errors were encountered: