Integrate two docker apps - Orthanc and OVIYAM - docker

I am trying to start two docker services. One is Orthanc and other is OVIYAM image viewer. My objective is to be able to view the images that I uploaded in Orthanc in Oviyam.
Step 1 - Upload images in Orthanc
Step 2 - View them in Oviyam
Though am currently able to start these two services, I am not able to integrate these two. I mean I did provide the listening port for OVIYAM which is 1025 in Orthanc.json.
To start Orthanc, I execute the below command
docker run -p 4242:4242 -p 8042:8042 --rm --name orthanc -v /home/test/abcd/abc/new_orthanc/orthanc.json:/etc/orthanc/orthanc.json -v /home/test/abcd/abc/new_orthanc/orthanc-db:/var/lib/orthanc/db jodogne/orthanc-plugins /etc/orthanc --verbose
To start Oviyam, I execute the below command
docker run -it --rm --name oviyam -p 8081:8080 -p 1025:1025 -v /home/test/abcd/abc/oviyam/data/:/usr/local/tomcat/work oviyam:2.7.1
I got the docker files for OVIYAM from this link (https://github.com/mocsharp/oviyam-docker) if that can help.
Though I am able to launch these services successfully, am not sure how I can integrate these two?
Am not sure how to setup this connection/integrate these two apps. Can you please help?

Depends on how those application communicate. If they talk to each other through network requests, you could use something like Docker Compose to start and link them together (https://docs.docker.com/compose/ , https://dev.to/mozartted/docker-networking--how-to-connect-multiple-containers-7fl).

Related

How to configure feature flags in Rabbitmq when using docker image?

I am trying to create a docker container with a rabbitMQ image, and then join that instance to an existing cluster.
However I get the error incompatible_feature_flags
It looks like the created image automatically enables some feature flags that are not enabled and cannot be enabled in the existing cluster.
I am running the container using the following code:
docker run -d --hostname xxx.yyy.com.co --name rabbit -p 15672:15672 -p 5672:5672 -p 4369:4369 --add-host='rabbit1:xxx.xxx.xx.xxx' --network=host -e RABBITMQ_DEFAULT_USER=admin -e RABBITMQ_DEFAULT_PASS=admin -e RABBITMQ_ERLANG_COOKIE='xxxxxxxx' -e ERL_EPMD_PORT=4369 rabbitmq:latest
I think that I can enable/disable feature flags as parameters when starting the container, but I have not been able to find anything in the documentation.
I would appreciate any help
It may be caused by the different version between the tow RabbitMQ applications.
eg: one is 3.7.x, but the another is 3.8.x .

How to set up xdebug / docker / drupal stack?

My objective is to be able to debug a tricky piece of Drupal 8 code. My experience with docker is very limited (beginner level). I have a database docker container running which I spinned like this:
docker run --name drupalMulti-database -p 3306:3306 -v `pwd`:/var/lib/mysql -d percona:latest
Then, my drupal 8 docker container is connected to the container above like this:
docker run -e XDEBUG_CONFIG="remote_host=10.1.2.74" --name drupalMulti -p 8484:80 -p 8453:443 --link drupalMulti-database:mysql -v `pwd`:/var/www/html/ -d gitlab.OUR-COMPANY-NAME.com:4999/dev/PATH-TO-OUR-DRUPAL-CONTAINER
I am wondering how can I configure either PhpStorm or VsCode to work properly with xdebug, so I could debug my drupal code: set breakpoints, step into the code etc? Assume that I have no access to modify the existing docker images, but my Drupal image already has xdebug pre-installed.
(Running Drupal 8 / php 7.2 / mysql 5.7)
Try setting xdebug.remote_host to host.docker.internal if the docker is running locally. You also would need to have a copy of the project stored locally to be able to debug it via PhpStorm. See https://www.jetbrains.com/help/phpstorm/configuring-xdebug.html#configuring-xdebug-docker and https://www.jetbrains.com/phpstorm/documentation/debugging/

Docker containers won't start again after being stopped

I'm trying to launch a GitLab or Gitea docker container in my QNAP NAS (Container Station) and, for some reason, when I restart the container, it won't start back up because files are lost (it seems).
For example, for GitLab it gives me errors saying runsvdir-start and gitlab-ctl don't exist. For Gitea it's the s6-supervise file.
Now I am launching the container like this, just to keep it simple:
docker run -d --privileged --restart always gitea/gitea:latest
A simple docker stop .... and docker start .... breaks it. How do I troubleshoot something like this?
QNAP has sent this issue to R&D and they were able to replicate it. It's a bug and will probably be fixed in a new Container Station update.
It's now fixed in QTS 4.3.6.20190906 and later.
Normal to lose you data if you launch just :
docker run -d --privileged --restart always gitea/gitea:latest
You should use VOLUME to sharing folder between your host and docker host for example :
docker run -d --privileged -v ./gitea:/data -p 3000:3000 -p 222:22 --restart always gitea/gitea:latest
Or use docker-compose.yml (see the official docs).

Link docker containers (Drupal and MariaDB)

To start I built a docker container from the MariaDB docker image.
After that I loaded a database dumpfile in the running container.
[MariaDB status][1]
Everything goes fine.
When I want to run/link the Drupal image:
docker run --name drupaldocker --link mariadbdocker:mariadb -p 8089:80 -d drupal
I can reach the drupal installation page, but when I want to load the database I always have the same errors:
-host, pass or dbname is wrong.
But I'm pretty sure my credentials are right.
It seems that my drupal container can't find the mariadb image.
Docker links is a deprecated feature and should be avoided: https://docs.docker.com/engine/userguide/networking/default_network/dockerlinks/
I assume you have a container named mariadbdocker running.
If you gain bash access inside drupaldocker container, you should be able to ping mariadb alias like this:
docker run --name drupaldocker --link mariadbdocker:mariadb -p 8089:80 -it drupal /bin/bash
If ping succeeds then you probably still have credentials issue.

Docker-local volume mount to the container:Connection refused

I am quite new to the world of docker and I am trying to set this up:
Running a solarwinds whd container and trying to mount a local volume on the host using this command:
docker run -d -p 8081:8081 --name=whdinstance -v pwd:/usr/local/webhelpdesk/bin/pgsql/var/lib/pgsql/9.2/data solarwinds/whd-embedded:latest
This starts the container and the volume is mounted but as soon as I go to localhost:8081 to login to the web helpdesk portal it asks me to select the database and then says "Connection refused" See Screenshot
can someone please help, if this might be an issue with the way I am mounting the volume?
Here exemples of how using volumes:
For use directory volume
docker run -itd -p 80:80 --name wordpress -v /path/in/your/host :/path/in/your/container wordpress
You have to put you -v and then the path of your directory in your container : the path of your shared directory on your host. When you done this you can choose your image !
So for you it should be something like
docker run -itd -p 8081:8081 --name=whdinstance -v /usr/local/webhelpdesk/bin/pgsql/var/lib/pgsql/9.2/data solarwinds/whd-embedded:latest

Resources