Repository navigation
Commit 30880a2
committed
Enable running Chrome in a sandbox
By default, Chrome wants to run in a sandbox for isolation. The
preferred way to do this would be to pass in a custom `seccomp` profile
to Docker, but this does not appear to be possible with a Dev
Containter because we can't provide a suitable path for one.
Instead, this does the less than ideal approach of disabling
confinement.
In the future, if it becomes possible to provide a path which can work
both locally and on Codespaces, we should be able to provide our own
list of syscalls it requires.
https://docs.docker.com/engine/security/seccomp/
https://stackoverflow.com/a/68876386
https://github.com/jessfraz/dotfiles/blob/main/etc/docker/seccomp/chrome.json
https://stackoverflow.com/a/64460373
devcontainers/cli#2101 parent 521e585 commit 30880a2
2 files changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
| 7 | + | |
7 | 8 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | | - | |
15 | 14 | | |
16 | 15 | | |
17 | 16 | | |
| |||
0 commit comments