Disclaimer: I'm posting this here because people started to vote to close this question on SO as "off-topic". Although some people believe Docker questions should be posted on SO as opposed to SF, others believe the opposite.

I have the following docker-compose.yml file which runs nginx with PHP support:

version: '3'
    container_name: my-app-nginx
    image: nginx:1.13.6
      - 8080:80
      - ./nginx-default.conf:/etc/nginx/conf.d/default.conf
      - ./my-app:/var/www/my-app
    restart: always
      - php
    container_name: my-app-php
    image: php:7.1-fpm
      - ./my-app:/var/www/my-app
    restart: always

The PHP application inside /var/www/my-app needs to communicate with a linux daemon (let's call it myappd).

The way I see it, I need to either:

  1. Copy the myappd into the nginx container to /usr/local/bin, make it executable with chmod +x and run it in the background.
  2. Create a different container, copy myappd to /usr/local/bin, make it executable with chmod +x and run it in the foreground.

Now, I'm new to Docker and I'm researching and learning about it but my best guess, given that I'm using Docker Composer, is that option 2 is probably the recommended one? Given my limited knowledge about Docker, I'd have to guess that this container would require some sort of linux-based image (like Ubuntu or something) to run this binary. So maybe option 1 is preferred? Or maybe option 2 is possible with a minimal Ubuntu image or maybe it's possible without such image?

Either way, I have no idea how would I implement that on the composer file. Especially option 2, how would the PHP application communicate with the daemon in a different container? Just "sharing" a volume (where the binary is located) like I did for nginx/php services would suffice? Or something else is required?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.