Nudebox: using with docker compose

[afitiskin]

Hello, I'm trying to use nudebox container as part of my application. I'm using docker-compose to run my application.

Here is my docker-compose.yml:

services:
  app:
    image: my_app_image
    environment:
      - 'ADULT_CHECK_HOST=nudebox'
      - 'ADULT_CHECK_PORT=8081'
      - 'ADULT_CHECK_PATH=/nudebox/check'
    links:
      - nudebox

  nudebox:
    image: 'machinebox/nudebox'
    restart: always
    ports:
      - '8081:8080'
    environment:
      - 'MB_KEY=my_key_here

Nudebox by itself is working fine (If i run docker-compose run nudebox i will get Box ready message).

When I try to start whole application with docker-compose up I'm getting following:

nudebox_1     | [INFO]     starting...
nudebox_1     |
nudebox_1     |     Welcome to Nudebox by Machine Box
nudebox_1     |     (nudebox development)
nudebox_1     |
nudebox_1     |     Visit the console to see what this box can do:
nudebox_1     |     http://localhost:8080
nudebox_1     |
nudebox_1     |     If you have any questions or feedback, get in touch:
nudebox_1     |     https://machinebox.io/contact
nudebox_1     |
nudebox_1     |     Please consider buying a subscription:
nudebox_1     |     https://machinebox.io/#pricing
nudebox_1     |
nudebox_1     |     Report bugs and issues:
nudebox_1     |     https://github.com/machinebox/issues
nudebox_1     |
nudebox_1     |     Tell us what you build on Twitter @machineboxio
nudebox_1     |
nudebox_1     | [ERROR]    post shutdown: accept tcp [::]:8080: use of closed network connection
nudebox_1     | [CRITICAL]    command exited during start up
nudebox_1     | 2018/05/02 16:43:01 command exited during start up

How can I fix the problem?

[matryer]

Hey @afitiskin - Make sure you give your Docker engine enough resources.

[ricktonoli]

@afitiskin Interested to know if this fixed your issue? Having a similar issue with facebox.

It did not fix it for me.

Is there any way to get more verbosity out of the logs, to see what it's doing. the [ERROR] on its own isn't particularly useful.

[afitiskin]

Moving container to more powerful server fixed my problem