Cannot build/run image locally

[saidmasoud]

When I try to clone this repo, and build/run the image locally, the below error message continues to print. I can pull the image directly from the Docker registry and run it successfully, though.

(The errors print forever....)

Here's what my docker-compose.yml looks like for this image:

services:
  stun:
    build:
      # The below dir contains the repo
      context: ./docker-turnserver
    container_name: stun
    ports:
      - 3478:3478
      - 3478:3478/udp
    network_mode: host
    restart: on-failure:10
    environment:
      - SKIP_AUTO_IP=true

[bprodoehl]

Thanks for the feedback. I’ll take a look, but there are a couple popular forks of my repo that get a lot more maintenance.

On Sat, Nov 18, 2017 at 2:06 PM Said Masoud notifications@github.com wrote:

When I try to clone this repo, and build/run the image locally, the below error message continues to print. I can pull the image directly from the Docker registry and run it successfully, though.

[image: image] https://user-images.githubusercontent.com/23317181/32984283-88cb28a2-cc71-11e7-9c20-5bf2c9faada7.png (The errors print forever....)

Here's what my docker-compose.yml looks like for this image:

services: stun: build:

The below dir contains the repo

  context: ./docker-turnserver
container_name: stun
ports:
  - 3478:3478
  - 3478:3478/udp
network_mode: host
restart: on-failure:10
environment:
  - SKIP_AUTO_IP=true

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bprodoehl/docker-turnserver/issues/7, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_uCUy5l2xQSbNMhIaopCmaixJs_y3Kks5s3zitgaJpZM4QjIWm .

-- -- http://www.connectify.me/

This email message is for the sole use of the intended recipient(s) and may contain Connectify confidential or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message.

[saidmasoud]

Ahh, I see. If there is a fork in particular which you think I should try instead, please let me know. I should be okay running the Docker registry image for now, thanks!