Run a Mendix Docker Image!

0
INFO: Adding uid to /etc/passwd INFO: Started Mendix Cloud Foundry Buildpack v4.3.3 [commit:Git_Com] WARNING: CF_INSTANCE_INDEX environment variable not found. Assuming responsibility for scheduled events execution and database synchronization commands. ERROR: Unable to fixup permissions of directory 'model' with mode 700: [Errno 1] Operation not permitted: '/opt/mendix/build/model', Ignoring. ERROR: Unable to fixup permissions of directory 'web' with mode 755: [Errno 1] Operation not permitted: '/opt/mendix/build/web', Ignoring. ERROR: Unable to fixup permissions of directory 'data' with mode 700: [Errno 1] Operation not permitted: '/opt/mendix/build/data', Ignoring. WARNING: External file store not configured, uploaded files in the app will not persist across restarts. See https://github.com/mendix/cf-mendix-buildpack for file store configuration details. INFO: Using Java version: INFO: openjdk version "11.0.3" 2019-04-16 INFO: OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.3+7) INFO: OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.3+7, mixed mode) INFO: Trying to start the MxRuntime... INFO - Logging: Logging to file: /opt/mendix/build/log/out.log, max size: 1099511627776KiB, max rotation: 10 INFO - Core: Mendix Runtime 8.6.0.715 (build 715). Copyright © 2003-2020 Mendix bv. All rights reserved. INFO - M2EE: Setting MaxFormContentSize for Runtime Server to 10485760 INFO - Services: Adding 0 authority certificate(s) INFO - ConnectionBus: Database product information: Microsoft SQL Server 15.00.2000 INFO - ConnectionBus: Database engine version: 15.0 INFO - ConnectionBus: Starting uniqueness constraint violation diagnostics... INFO - ConnectionBus: Uniqueness constraint violation diagnostics has been successfully finished. No violations are found. INFO - Core: Storage service: Local file system storage, uploaded files path: /opt/mendix/build/data/files INFO - ConnectionBus: Database: Microsoft SQL Server 15.00.2000, name: 'mendix' Driver: Microsoft JDBC Driver 7.2 for SQL Server 7.2.1.0 Mar 18, 2020 7:35:26 AM java.util.prefs.FileSystemPreferences$6 run WARNING: Prefs file removed in background /opt/mendix/build/.java/.userPrefs/com/mendix/core/prefs.xml WARNING - Core: The runtime has been started using a trial license, the framework will be terminated when the maximum time is exceeded! INFO - Core: Running after-startup-action... WARNING - MendixSSO: NOT starting MendixSSO request handlers, as it is disabled by the configuration INFO - Core: Successfully ran after-startup-action. INFO - ActionManager: Scheduling MendixSSO.SE_CleanupAuthRequest every 1 hour, starting from 2018-11-01 00:00:00 (UTC) INFO - ActionManager: Scheduling MendixSSO.DeleteExpiredTokens every 1 hour, starting from 2019-01-01 00:00:00 (UTC) INFO - Core: Mendix Runtime successfully started, the application is now available. INFO: The MxRuntime is fully started now. INFO: Ensuring admin user credentials INFO: Model version: unversioned INFO: MENDIX-INTERNAL: Metrics are disabled. INFO: MENDIX-LOGGING-HEARTBEAT: Heartbeat number 1   How do I solve it?    
asked
2 answers
4

Hi  SeungMin Kim,

Try to check your command line it should be a like below command.

docker run -it -p 8080:8080 -e ADMIN_PASSWORD=Password1! -e DATABASE_ENDPOINT=postgres://postgres:admin@localhost:5432/{dbname} {image-name}

 

when you try to give like this you should not get any database connection error.

 

Host Name you should try like this:

1)localhost (or)

2)host.docker.internal  (or)

3)docker.for.win.localhost (if you using windows)

answered
0

If you get this at the end...

INFO - Core: Mendix Runtime successfully started, the application is now available.
INFO: The MxRuntime is fully started now.
INFO: Ensuring admin user credentials
INFO: Model version: unversioned
INFO: MENDIX-INTERNAL: Metrics are disabled.
INFO: MENDIX-LOGGING-HEARTBEAT: Heartbeat number 1

...then the container has started successfully. Have you tried connecting to the application with your browser?

answered