Firefox 68.x won't run (from inside docker)
See original GitHub issueI’ve used FirefoxHeadless inside docker just fine for a long time - but with v68 of ffox it just won’t work.
19:02:46 [32m09 08 2019 17:02:44.991:INFO [launcher]: [39mStarting browser FirefoxHeadless
19:03:54 [33m09 08 2019 17:03:45.123:WARN [launcher]: [39mFirefoxHeadless have not captured in 60000 ms, killing.
19:03:54 [32m09 08 2019 17:03:45.598:INFO [launcher]: [39mTrying to start FirefoxHeadless again (1/2).
19:04:54 [33m09 08 2019 17:04:45.602:WARN [launcher]: [39mFirefoxHeadless have not captured in 60000 ms, killing.
19:04:54 [32m09 08 2019 17:04:45.724:INFO [launcher]: [39mTrying to start FirefoxHeadless again (2/2).
19:05:50 [33m09 08 2019 17:05:45.855:WARN [launcher]: [39mFirefoxHeadless have not captured in 60000 ms, killing.
19:05:50 [91m09 08 2019 17:05:47.109:ERROR [launcher]: [39mFirefoxHeadless failed 2 times (timeout). Giving up.
Karma config:
// Karma configuration file, see link for more information
// https://karma-runner.github.io/0.13/config/configuration-file.html
//https://hackernoon.com/running-karma-tests-with-headless-chrome-inside-docker-ae4aceb06ed3
const isDocker = require('is-docker')();
module.exports = function (config) {
config.set({
concurrency: 1, // avoid clash when ffox and chrome run at the same time
customLaunchers: {
ChromeCustom: {
base: 'ChromeHeadless',
// We must disable the Chrome sandbox when running Chrome inside Docker (Chrome's sandbox needs
// more permissions than Docker allows by default)
flags: isDocker ? ['--no-sandbox'] : []
}
},
basePath: '',
frameworks: ['jasmine', '@angular-devkit/build-angular'],
plugins: [
require('karma-jasmine'),
require('karma-coverage'),
require('karma-coverage-istanbul-reporter'),
require('karma-chrome-launcher'),
require('karma-firefox-launcher'),
require('karma-junit-reporter'),
//require('karma-remap-istanbul'),
require('@angular-devkit/build-angular/plugins/karma')
],
files: [
],
preprocessors: {
'./src/app/**/*.ts': ['coverage']
},
coverageReporter: {
type:'lcov',
dir:'target/coverage'
},
mime: {
'text/x-typescript': ['ts','tsx']
},
angularCli: {
config: './angular-cli.json',
environment: 'dev'
},
reporters: config.angularCli && config.angularCli.codeCoverage
? ['progress', 'junit','coverage-istanbul','coverage']
: ['progress', 'junit'],
junitReporter: {
outputDir: 'target/junit-reports'
//outputDir: 'target/junit-dir: require('path').join(__dirname, 'coverage'), reports'
},
port: 9876,
colors: true,
autoWatch: true,
browsers: ['FirefoxHeadless','ChromeCustom'],
singleRun: false
});
};
Image I am using: https://hub.docker.com/r/evryfs/node-dev-docker/ (node12 tag)
Issue Analytics
- State:
- Created 4 years ago
- Comments:49
Top Results From Across the Web
Firefox hangs with Xephyr, both running inside an LXC ...
X11-unix is bind-mounted inside the container in read-only, so the Xephyr running inside the container cannot create its socket there.
Read more >Reproducing the Linux builds of Firefox 68 - glandium.org
The command output will give you a docker run -ti ... command to try. Run it. It will open a shell in the...
Read more >Full Ubuntu GUI in a Container Displayed on Windows (XServer)
Run Ubuntu Desktop Environment in a Docker Container and Display on Windows.---00:00 Introduction00:34 XServer on Windows00:52 Build Lubuntu ...
Read more >Headless firefox docker - cittafamiglia.it
This is a headless Firefox image, with Splinter running. ... Firefox 68 headless is not working inside docker containers x won t run...
Read more >Firefox/Tweaks - ArchWiki - Arch Linux
Set image.mem.max_decoded_image_kb to at least 512K. Now scrolling should flow smoothly. Run Firefox inside an nspawn container. See systemd- ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Facing the same problem with gitlab-ci using firefox-esr 68 from debian buster.
Setting
MOZ_FORCE_DISABLE_E10S=true
made things work again.Oh, that’s super helpful. So know we now that at least it is finding the binary.
Digging into related issues, this seems really promising:
Specifically, it points to problems with shared memory affecting firefox running in docker containers and includes:
karma-firefox-launcher
likewise includesuser_pref("browser.tabs.remote.autostart", false)
(anduser_pref("browser.tabs.remote.autostart.2", false)
).The solution seems to be running docker with
--shm-size 2g
or mounting-v /dev/shm:/dev/shm
.See:
Ultimately, though it seems like this is tracked by: