Steps to Reproduce
- Go to proton root directory
- Build production image from blubber file
cat .pipeline/blubber.yaml | curl -s -H "Content-Type: application/yaml" --data-binary @- "https://blubberoid.wikimedia.org/v1/production" | docker build --tag proton --file - .
- Run the container
docker run -it -p "3030:3030" --env APP_ENABLE_CANCELLABLE_PROMISES=true proton
Expected Results
- Service logs no errors and can be accessed via http://localhost:3030
Actual Results
{"name":"proton","hostname":"847a94968a1d","pid":1,"level":60,"err":{"message":"","name":"Error","stack":"Error: ENOENT: no such file or directory, access '/usr/bin/chromium'\n at Error (native)","code":"ENOENT","cause":{"errno":-2,"code":"ENOENT","syscall":"access","path":"/usr/bin/chromium"},"isOperational":true,"errno":-2,"syscall":"access","path":"/usr/bin/chromium","levelPath":"fatal/service-runner/worker"},"msg":"ENOENT: no such file or directory, access '/usr/bin/chromium'","time":"2019-11-22T02:36:39.232Z","v":0}
Additional notes
- The other images (development and test) work fine