I ran docker-compose up and shows blank page on http://localhost:8080/

senaka · September 9, 2020, 3:18pm

Hi All,
I am new to metasfresh and I select to go with the docker option on Windows 10. I ran the docker-compose up and it seems up the WebUI on port 8080 but seems error in DB.
Could you please advise me on this.

Regards
Senaka

Creating metasfresh-docker_db_1 … done
Creating metasfresh-docker_rabbitmq_1 … done
Creating metasfresh-docker_search_1 … done
Creating metasfresh-docker_app_1 … done
Creating metasfresh-docker_webapi_1 … done
Creating metasfresh-docker_webui_1 … done
Attaching to metasfresh-docker_search_1, metasfresh-docker_db_1, metasfresh-docker_rabbitmq_1, metasfresh-docker_app_1, metasfresh-docker_webapi_1, metasfresh-docker_webui_1
app_1 | standard_init_linux.go:211: exec user process caused “no such file or directory”
db_1 |
db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1 |
db_1 | FATAL: data directory “/var/lib/postgresql/data” has wrong ownership
db_1 | HINT: The server must be started by the user that owns the data directory.
rabbitmq_1 | 2020-09-09 14:57:49.686 [info] <0.33.0> Application lager started on node rabbit@90552404bf91
search_1 | [2020-09-09 14:57:25,733][WARN ][bootstrap ] unable to install syscall filter: seccomp unavailable: your kernel is buggy and you should upgrade
search_1 | [2020-09-09 14:57:27,360][INFO ][node ] [Solara] version[2.4.6], pid[1], build[5376dca/2017-07-18T12:17:44Z]
search_1 | [2020-09-09 14:57:27,360][INFO ][node ] [Solara] initializing …
search_1 | [2020-09-09 14:57:30,657][INFO ][plugins ] [Solara] modules [reindex, lang-expression, lang-groovy], plugins [], sites []
webapi_1 | standard_init_linux.go:211: exec user process caused “no such file or directory”
search_1 | [2020-09-09 14:57:31,040][INFO ][env ] [Solara] using [1] data paths, mounts [[/usr/share/elasticsearch/data (grpcfuse)]], net usable_space [133.6gb], net total_space [221.6gb], spins? [possibly], types [fuse.grpcfuse]
search_1 | [2020-09-09 14:57:31,041][INFO ][env ] [Solara] heap size [247.5mb], compressed ordinary object pointers [true]
search_1 | [2020-09-09 14:57:43,922][INFO ][node ] [Solara] initialized

senaka · September 13, 2020, 3:08pm

I tried with a fresh approach. Just mapping default port for wbeui. (port 80 . I mean HTTP://localhost), Still I only get a blank page. In the docker dashboard shows db and webapi containers starting not running.
Could please advise me.

julian.bischof · September 15, 2020, 7:08am

Hi @senaka

Generally, we recommend running the metasfresh server docker installation on a Linux Server ( Ubuntu Server works pretty well ).

The permission error in Windows for the postgres database container looks like a very common issue:

github.com/docker/for-win

Mounting data volume for Postgres in docker for Windows doesn't work

opened 02:22PM - 30 Jan 17 UTC

closed 04:51PM - 30 Jan 17 UTC

vrindanayak

lifecycle/locked

### Expected behavior Postgres should start and mount the correct windows direc…tory as a data volume ### Actual behavior ```` The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.utf8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /var/lib/postgresql/data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting dynamic shared memory implementation ... posix creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok initdb: could not fsync file "/var/lib/postgresql/data/base/1": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/base/12406": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/base/12407": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/base": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/global": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_clog": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_commit_ts": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_dynshmem": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_logical/mappings": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_logical/snapshots": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_logical": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_multixact/members": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_multixact/offsets": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_multixact": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_notify": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_replslot": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_serial": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_snapshots": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_stat": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_stat_tmp": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_subtrans": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_tblspc": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_twophase": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_xlog/archive_status": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_xlog": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data": Invalid argument initdb: could not fsync file "/var/lib/postgresql/data/pg_tblspc": Invalid argument WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. syncing data to disk ... ok Success. You can now start the database server using: pg_ctl -D /var/lib/postgresql/data -l logfile start waiting for server to start....FATAL: data directory "/var/lib/postgresql/data" has wrong ownership HINT: The server must be started by the user that owns the data directory. pg_ctl: could not start server Examine the log output. stopped waiting ```` ### Information docker-compose.yml file : ```` version: "2" services: slapd: image: dcm4che/slapd-dcm4chee:2.4.40-8.1 ports: - "389:389" env_file: docker-compose.env volumes: - //c/Users/<user>/var/local/dcm4chee-arc/ldap:/var/lib/ldap - //c/Users/<user>/var/local/dcm4chee-arc/slapd.d:/etc/ldap/slapd.d postgres: image: dcm4che/postgres-dcm4chee:9.6-8 ports: - "5432:5432" env_file: docker-compose.env volumes: - //c/Users/<user>/var/local/dcm4chee-arc/db:/var/lib/postgresql/data dcm4chee-arc: image: dcm4che/dcm4chee-arc-psql:5.8.1 ports: - "8080:8080" - "9990:9990" - "11112:11112" - "2575:2575" env_file: docker-compose.env environment: WILDFLY_CHOWN: /opt/wildfly/standalone /storage WILDFLY_WAIT_FOR: ldap:389 db:5432 AUTH_SERVER_URL: /auth JAVA_OPTS: "-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true" links: - slapd:ldap - postgres:db volumes: - //c/Users/<user>/var/local/dcm4chee-arc/storage:/storage - //c/Users/<user>/var/local/dcm4chee-arc/wildfly:/opt/wildfly/standalone ```` Note : Substituted `<user>` with my user docker-compose.env file ```` LDAP_BASE_DN=dc=dcm4che,dc=org LDAP_ORGANISATION=dcm4che.org LDAP_ROOTPASS=secret LDAP_CONFIGPASS=secret ARCHIVE_DEVICE_NAME=dcm4chee-arc AE_TITLE=DCM4CHEE DICOM_HOST=localhost DICOM_PORT=11112 HL7_PORT=2575 STORAGE_DIR=/storage/fs1 POSTGRES_DB=pacsdb POSTGRES_USER=pacs POSTGRES_PASSWORD=pacs WILDFLY_ADMIN_USER=admin WILDFLY_ADMIN_PASSWORD=admin KEYCLOAK_ADMIN_USER=admin KEYCLOAK_ADMIN_PASSWORD=admin ```` ### Steps to reproduce the behavior 1. Share Drive using Docker for Windows->Settings->Shared Drive -> C: 2. Use _docker-compose up -d_ Similar issue was already reported on https://github.com/docker/docker/issues/25908 but was redirected here to be checked/opened on https://github.com/docker/for-win/issues I have searched for this issue in Open and Closed issues list, but couldn't find any. I'm using - Windows 10 Pro, 64-bit - Docker version 1.13.0, build 49bf474

If you really want to run the server in Windows 10 Linux Subsystem, I suggest checking out the issues (and solutions) in the links above.

Alternatively you could just create a Virtualbox machine on your Windows environment with a Ubuntu Server 20.04 installation and try to deploy metasfresh that way (please note the hardware requirements here when setting up the virtual machine: How to set up the metasfresh stack using Docker? )

Anyway, please let us know which approach you chose and if you try the Windows 10 docker installation and managed to solve it, consider sharing your solution here so others may find your answer.

senaka · September 21, 2020, 3:35am

Hi Julian,
Thank you for your reply. I will first try out on Ubuntu.
If I succeed in Windows 10, definitely share here.

Regards
Senaka