docker-mendix-buildpack
docker-mendix-buildpack copied to clipboard
mendix
Docker run is getting failed
I am using Windows machine where I am running docker. Docker Build is getting succeed , but issue while Docker Run command.
Docker Run Command:
docker run -it -e ADMIN_PASSWORD=Password1! -e DATABASE_ENDPOINT=mysql://root:root@localhost:3306/a <imagename:tagname>
Error:
INFO: Started Mendix Cloud Foundry Buildpack v3.2.4 [commit:unknown_commit]
WARNING: CF_INSTANCE_INDEX environment variable not found. Assuming responsibility for scheduled events execution and database synchronization commands.
sed: can't read .local/m2ee.yaml: No such file or directory
Traceback (most recent call last):
File "/opt/mendix/buildpack/start.py", line 1296, in <module>
pre_process_m2ee_yaml()
File "/opt/mendix/buildpack/start.py", line 152, in pre_process_m2ee_yaml
".local/m2ee.yaml",
File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sed', '-i', 's|BUILD_PATH|/opt/mendix/build|g; s|RUNTIME_PORT|8081|; s|ADMIN_PORT|8082|; s|PYTHONPID|6|', '.local/m2ee.yaml']' returned non-zero exit status 2
ERROR: Failed to terminate all child processes
Traceback (most recent call last):
File "/opt/mendix/buildpack/start.py", line 1108, in terminate_process
os.killpg(this_process, signal.SIGTERM)
ProcessLookupError: [Errno 3] No such process
I have seen this behaviour with other customers on Windows. Something seems wrong with the way how Windows preserves the permissions on the files, workaround is to run the Docker build on Linux (e.g. in a VM).
Tried with Linux as well, but no luck. Getting same error on linux as well. Are there any pre-requisites for running the docker image on linux machine ? @MXClyde , Are you able to run it on your environment ?
Nope, no prerequisites other than Docker. Yes, I have it running on 10+ environments. You might want to try a release prior to 2.0.0 as they run as root.
I am getting the same error running on a Mac. Has anyone found a solution? Thanks.
Hey did you find any solution . I'm also facing the same issue. Getting an error on Debian.
