question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Support]: docker-compose hangs with no error message

See original GitHub issue

Describe the problem you are having

Spend the day setting up a bare metal Debian 11 server to use for Frigate. I think I’ve got the server all setup but running docker-compose up results the following messages, but just hangs until CTRL + C to close it.

Can you see what the issue is?

user@system:~/Documents/frigate$ docker-compose up
[+] Running 2/0
 ⠿ Container mqtt     Created                                                                                   0.0s
 ⠿ Container frigate  Created                                                                                   0.0s
Attaching to frigate, mqtt
mqtt     | 1656903544: mosquitto version 1.6.15 starting
mqtt     | 1656903544: Config loaded from /mosquitto/config/mosquitto.conf.
mqtt     | 1656903544: Opening ipv4 listen socket on port 1883.
mqtt     | 1656903544: Opening ipv6 listen socket on port 1883.
mqtt     | 1656903544: mosquitto version 1.6.15 running
frigate  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
frigate  | [s6-init] ensuring user provided files have correct perms...exited 0.
frigate  | [fix-attrs.d] applying ownership & permissions fixes...
frigate  | [fix-attrs.d] done.
frigate  | [cont-init.d] executing container initialization scripts...
frigate  | [cont-init.d] done.
frigate  | [services.d] starting services
frigate  | [services.d] done.

Version

NA

Frigate config file

mqtt:
  host: 127.0.0.1
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  stats_interval: 60
logger:
  default: info
record:
  enabled: False
snapshots:
  enabled: False
rtmp:
  enabled: True
cameras:
  testCam:
    ffmpeg:
      - input_args:
        - -c:v
        - h264
      - path: rtsp://192.168.0.22:554/s1
        roles: 
          - rtmp
    mqtt:
      enabled: True
      timestamp: True
      bounding_box: True
      height: 720
      quality: 70

Relevant log output

NA

FFprobe output from your camera

NA

Frigate stats

NA

Operating system

Debian

Install method

Docker Compose

Coral version

CPU (no coral)

Network connection

Wired

Camera make and model

UniFi G3 Flex

Any other information that may be helpful

docker-compose file:

version: "3"
services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    image: blakeblackshear/frigate:stable-amd64nvidia
    runtime: nvidia
    environment:
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=compute,utility,video
    shm_size: "256mb"
    devices:
      - /dev/dri/rederD128
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8080:8080"
    command: /bin/sh -c "while sleep 1000; do :; done"
  mqtt:
    container_name: mqtt
    image: eclipse-mosquitto:1.6
    ports:
      - "1883:1883"

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:20 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
blakeblackshearcommented, Jul 4, 2022

You are still using parts of the development compose file. At the very least, you need to remove the following line that prevents Frigate from running:

command: /bin/sh -c "while sleep 1000; do :; done"

Also, compare the rest of the compose file to the example in the docs.

1reaction
NickM-27commented, Jul 4, 2022

The container port you are exposing is 8080. Frigate runs on 5000 internally

The MQTT setting in the config file is the localhost for the frigate container. Were the containers attached to the host network that would be fine as that would be the host machine but as you are creating both frigate and mqtt in the same docker-compose file a new bridge network is created and both frigate and mqtt will have differing IP addresses on that network. Use the mqtt container name (so mqtt) as the host in the MQTT section of your config.yml file and that way it will be resolved to whatever the ip address of the mqtt container is

Yep, both of these are correct. 127.0.0.1 is localhost so mqtt config section needs to be adjusted. Also port 5000 needs to be exposed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

docker-compose up hangs forever. How to debug?
If even docker-compose --version hangs, this might be your fix. Docker-compose seems to hang indefinitely when the system has low entropy.
Read more >
Known issues for Docker Desktop on Mac
We have written a detailed report on this. You might encounter errors when using docker-compose up with Docker Desktop ( ValueError: Extra Data...
Read more >
Docker Engine release notes
This release of Docker Engine contains updated versions of Docker Compose, Docker Scan, Containerd, added packages for Ubuntu 22.10, and some minor bug...
Read more >
Overview | Docker Documentation
This page contains information on: How to diagnose and troubleshoot Docker Desktop issues; Check the logs; Find workarounds for common problems ...
Read more >
docker compose kill
docker compose kill: Forces running containers to stop by sending a `SIGKILL` signal. ... docker compose kill. Force stop service containers.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found