Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot build/run the modeler as docker

See original GitHub issue

Describe the Bug

I cannot start the camuda-modeler. I get the following error:

camunda-modeler-builder@0.0.0 app:dev /home/modeler electron ./app/dev.js --force-update-checks resources/diagram/simple.bpmn [134:1127/072806.341331:FATAL:atom_main_delegate.cc(211)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. camunda-modeler-client@4.4.0 dev /home/modeler/client run-s start camunda-modeler-client@4.4.0 start /home/modeler/client cross-env NODE_ENV=development webpack-dev-server --config ./webpack.config.js --port 3000 sh: 1: cross-env: not found npm ERR! code ELIFECYCLE npm ERR! syscall spawn

Steps to Reproduce

In order to reproduce, download the release 4.4.0 as a zip and unpack it then run the attached docker file Dockerfile.txt from inside the folder

Then run the container with: docker run --network=host -it imagename . Switch to posix enabled terminal bash --posix and go in the /modeler folder. Run npm install and then npm start, you will see the error

Expected Behavior The system should start

Environment

OS: ubuntu:bionic
Camunda Modeler Version: 4.4.0

Issue Analytics

State:
Created 3 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

nikkucommented, Nov 28, 2020

Happy that you got the basics running and shared your solution. It is great how far you got.

To clarify though we cannot support you in running the development setup of the App inside docker. We do in no way recommend that setup, too. There is many things wrong about it, including (but not limited to) potential poor performance and pain to set it up (you experienced it).

I’ll close this issue as you were able to get things running.

However, once inside I encounter the issue that I need to run npm start twice. The first one seems is “warming up” everything (I need to wait for output of webpack). The second one, then shows camuda working.

This is expected behavior, with or without docker. You’ll initially see an empty page and have to CMD/CTRL + R in order to refresh the app once the initial webpack bundle completed.

1reaction

matteopantanocommented, Nov 27, 2020

For me it is a requirement to get it running in a docker container. I was already able to dockerize the bpmnjs so this should be just a step-further. Your suggestion would be for a non-root user?

Top Results From Across the Web

Run your tests - Docker Documentation

Open the src/test/java/org/springframework/samples/petclinic/model/ValidatorTests.java file and change the assertion. assertThat(violation.getMessage()).

How to Build, Run and Upload your Docker image ... - Medium

In this scope we have implemented an application that has a trained Mask RCNN model in order to characterize metal material powders that...

Unable to Train Tensorflow Model Container in Sagemaker ...

I'm fairly new to Sagemaker and Docker.I am trying to train my own custom object detection algorithm in Sagemaker using an ECS container....

10 things to avoid in docker containers | Red Hat Developer

First: Containers are immutable - The OS, library versions, configurations, folders, and application are all wrapped inside the container. You ...

Docker toolchain | CLion Documentation - JetBrains

Docker toolchain. Last modified: 28 December 2022. OS: macOS / Linux / Windows. Project model: CMake/Makefile. For the purpose of development in Docker...