docker-mendix-buildpack icon indicating copy to clipboard operation
docker-mendix-buildpack copied to clipboard

Build and Run Mendix in Docker

Results 53 docker-mendix-buildpack issues
Sort by recently updated
recently updated
newest added

On running make build-image I receive the below error. Is this somehow a missing dependency? `make build-image docker build \ --build-arg BUILD_PATH=build \ -t mendix/mendix-buildpack:v1.3 . Sending build context to...

Hi, we are using this tool extensively in our projects. The bloated size of the images are really becoming an issue for us. I've put in a ticket with support...

Mendix images are typically quite huge, making size an issue (see #80). This could be helped somewhat by choosing a smaller base image for the 'rootfs'. For example, I typically...

$ make run-container docker-compose -f tests/docker-compose-mysql.yml up Pulling mendixapp (mendix/mendix-buildpack:v1.3)... The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost....

The current provided Makefile is not compatible with Windows ....

It would be useful if the CERTIFICATE_AUTHORITIES variable could also be a file At the moment we have added a hack to startup (.py) in order to copy the contents...

Building the pack in Windows will cause problems due to permissions settings in the resulting linux container. Could you please consider revamping the structure in a way that you move...

Can you please add some troubleshooting document which can tell what issues can occur while building and running the images along with their fixes.

: No such file or directory The command '/bin/sh -c "/buildpack/compilation" /build /cache && rm -fr /cache /tmp/javasdk /tmp/opt' returned a non-zero code: 127 make: *** [build-image] Error 127

The APPMETRICS_TARGET variable needs to be non-empty on build time for the telegraf agent to be included in the container.