[arch-general] Chromium in a systemd-nspawn container?

Christian Rebischke Chris.Rebischke at archlinux.org
Sat Feb 22 10:13:46 UTC 2020

On Fri, Feb 21, 2020 at 05:59:44PM +0000, Mark Raynsford via arch-general wrote:
> Hello!
> It seems that a recent update (unfortunately, I'm not sure exactly
> which) broke my ability to run Chromium in a systemd-nspawn container.
> Specifically, the symptom is that the Chromium window opens, but
> remains blank and evidently doesn't respond to keyboard/mouse input.
> Firefox in the same container runs without issue.
> Is there something I can do to debug this issue? I'm using the standard
> trick to allow containers to access X:
>   https://wiki.archlinux.org/index.php/Systemd-nspawn#Use_an_X_environment
> The only possibly relevant error message I see on Chromium's stderr is:
>   67:67:0221/100217.520256:ERROR:gpu_channel_manager.cc(459)]
>   ContextResult::kFatalFailure: Failed to create shared context for
>   virtualization.
> I've tried the --disable-gpu flag, but that makes no difference.
> Any ideas?

Hello Mark,

you need to disable a few flags:

--disable-software-rasterizer, --disable-dev-shm-usage and --disable-web-security

See also: https://github.com/Zenika/alpine-chrome/issues/36#issuecomment-534392761

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20200222/b2f19c27/attachment.sig>

More information about the arch-general mailing list