headless_shell in a docker container

[Alex Vaghin]

Trying to run headless_shell in a docker container:

[0722/100306:FATAL:v8_initializer.cc(304)] Couldn't mmap v8 natives data file, status code is 1
#0 0x0000048e7d0e base::debug::StackTrace::StackTrace()
#1 0x00000492a09f logging::LogMessage::~LogMessage()
#2 0x000006b0c700 gin::V8Initializer::LoadV8Natives()
#3 0x00000456511f content::ContentMainRunnerImpl::Initialize()
#4 0x000004554209 content::ContentMain()
#5 0x0000047e8f96 headless::(anonymous namespace)::RunContentMain()
#6 0x0000047e92a1 headless::HeadlessBrowserMain()
#7 0x0000004287e3 main
#8 0x7f8d45cd6b45 __libc_start_main
#9 0x000000427f71 <unknown>

While running perfectly fine outside of container. The run command is as follows:

headless_shell ----remote-debugging-port=9222 about:blank

The binary was built using instructions on https://chromium.googlesource.com/chromium/src/+/master/headless

Any ideas. Is that expected?

[PhistucK]

https://groups.google.com/a/chromium.org/d/forum/headless-dev might be a better venue for this.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[Eric Seckler]

[cc headless-dev, bcc chromium-discuss]

Sounds like this may be an issue related to how you package headless_shell for docker. Maybe there are some files missing? There's a thread suggesting that.