David J. M. Karlsen

I have also seen those issues and tried running with `shm_size 2g` but the problem persist

@brendandahl ``` 20:55:12 19 08 2019 18:55:11.424:INFO [karma-server]: Karma v4.2.0 server started at http://0.0.0.0:9876/ 20:55:12 19 08 2019 18:55:11.428:INFO [launcher]: Launching browsers FirefoxHeadless, ChromeCustom with concurrency 1 20:55:12 19 08...

hang on! That actually got further. I had some bad config. It might actually fail on a bad test.

Yes - that version consistently works OK! https://github.com/evryfs/node-dev-docker/blob/ffoxbroken/Dockerfile

+1 - ran into this myself. If you run the ct command natively it will provide more output. I believe this is because the stdout is lost in the docker...

Both comments are reasonable: * configurable branch name (default gh_branches) * pr or push, with configured branch as target, for a pr you need a pr branch name as well,...

Any update here @gmorse81 ?

Should PodDisruptionBudget be added too? https://kubernetes.io/docs/tasks/run-application/configure-pdb/ . Also see https://github.com/helm/charts/blob/master/stable/nginx-ingress/templates/controller-poddisruptionbudget.yaml - one thing to note is to not enable it if replicacount == 1 as this disables eviction

Ah - I missed the fact that it was already mentioned. But yes - a complete example-chart would be very nice and the easiest to point to.

ECR has some quirks where you exchange an IAM user/creds into docker creds which are valid for 6hrs. https://github.com/evryfs/helm-charts/tree/master/charts/ecr-proxy is one solution. There are also other variants which create pullsecrets...