Change SecurityOptions with colima start --edit #1019
gibbardsteve
started this conversation in
General
Replies: 1 comment
-
What errors are you getting? I may be having the same problem. I'm trying to run Supabase, which I was able to do with Docker Desktop running. But with Colima I get tons of
My Docker info shows:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
TLDR; How do I disable apparmor in Security Options using colima start --edit (I see it enabled when running docker info)?
I am experiencing a failing container when using colima, but when I run with docker desktop the container works fine. I think I have narrowed it down to a permissions issue when mounting directories. What I would like to do in Colima is set the docker config to match the working docker desktop scenario to see if that is the issue.
running docker info in working scenario (docker desktop):
Security Options:
seccomp
Profile: unconfined
cgroupns
running docker info in colima:
Security Options:
apparmor
seccomp
Profile: unconfined
cgroupns
How can I edit the colima config template to indicate apparmor is disabled?
My current config in the template file (when I run colima start --edit) is:
docker:
seccomp-profile: unconfined
I have tried apparmor: false but this doesn't work.
Beta Was this translation helpful? Give feedback.
All reactions