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]: amd64 docker container exits after "[Errno -2] Name or service not known"

See original GitHub issue

Describe the problem you are having

I cannot get the container to start. Using docker-compose, python 3.8 on ubuntu server 20.04. Server’s name is “kathy,” running MQTT broker in another container on port 1883. Other containers can access MQTT broker.

Any help would be appreciated.

Docker compose file:

version: "3.3"
services:
  frigate:
    container_name: frigate
    image: blakeblackshear/frigate:stable-amd64
    restart: unless-stopped
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /media/raid/allshare/frigateconf/config.yml:/config/config.yml:ro
      - /media/camdrive/frigate:/media/frigate
    ports:
      - "5000:5000"
      - "1935:1935"
    environment:
      FRIGATE_RTSP_PASSWORD: "password"

Version

0.9.2-25bb515 (from log file)

Frigate config file

mqtt:
  host: kathy:1883

cameras:
  camera1:
    ffmpeg:
      inputs:
        - path: "rtsp://user:pass@192.168.1.254:554"
          roles:
            - rtmp
            - detect
    detect:
      width: 2688
      height: 1520

Relevant log output

Creating frigate ... done
Attaching to frigate
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.
frigate    | [2021-10-23 10:31:46] frigate.app                    INFO    : Starting Frigate (0.9.2-25bb515)
frigate    | [2021-10-23 10:31:46] frigate.app                    INFO    : Creating directory: /tmp/cache
frigate    | Starting migrations
frigate    | [2021-10-23 10:31:46] peewee_migrate                 INFO    : Starting migrations
frigate    | There is nothing to migrate
frigate    | [2021-10-23 10:31:46] peewee_migrate                 INFO    : There is nothing to migrate
frigate    | [Errno -2] Name or service not known
frigate    | [cmd] python3 exited 1
frigate    | [cont-finish.d] executing container finish scripts...
frigate    | [cont-finish.d] done.
frigate    | [s6-finish] waiting for services.
frigate    | [s6-finish] sending all processes the TERM signal.
frigate    | [s6-finish] sending all processes the KILL signal and exiting.

FFprobe output from your camera

n/a

Frigate stats

n/a

Operating system

Debian

Install method

Docker Compose

Coral version

CPU (no coral)

Network connection

Wired

Camera make and model

Amcrest

Any other information that may be helpful

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
jasdmeyercommented, Oct 23, 2021

I tried with the IP address, without the port number. I think I missed that earlier. The container started right up!

Thanks!

2reactions
blakeblackshearcommented, Oct 23, 2021

remove the port from the hostname

Read more comments on GitHub >

github_iconTop Results From Across the Web

Docker container having issue communicating to local server ...
Description Attempting to use a Flow within Docker from ... Failed to establish a new connection: [Errno -2] Name or service not known...
Read more >
Why docker container exits immediately - Stack Overflow
My pracitce is in the Dockerfile start a shell which will not exit immediately CMD [ "sh", "-c", "service ssh start; bash"] ,...
Read more >
Why new Macs break your Docker build, and how to fix it
Solution #2: Run x86_64 Docker images instead​​ In Compose you can also use the platform option per-service. With any of these options you...
Read more >
docker run - Docker Documentation
--restart, no, Restart policy to apply when a container exits ... If the specified image is not found, an error is produced, and...
Read more >
Docker run reference
Do not pass a service x start command to a detached container. ... docker: Error response from daemon: Container command 'foo' not found...
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