Docker container is running but is refusing all connections

[bitbythecron]

Which version are you using?

Current latest docker image

Which operating system are you using?

• macOS amd64 Docker

Describe the issue

I had asked this as a question previously but after playing around a bit more I'm almost certain this is a bug in the Dockerfile. I am running MediaMTX via docker like so:

docker run --rm -it --network=host bluenviron/mediamtx:latest             
2023/10/16 15:05:22 INF MediaMTX v1.2.0
2023/10/16 15:05:22 INF configuration loaded from /mediamtx.yml
2023/10/16 15:05:22 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
2023/10/16 15:05:22 INF [RTMP] listener opened on :1935
2023/10/16 15:05:22 INF [HLS] listener opened on :8888
2023/10/16 15:05:22 INF [WebRTC] listener opened on :8889 (HTTP)
2023/10/16 15:05:22 INF [SRT] listener opened on :8890 (UDP)

I can confirm that it is running:

docker ps
CONTAINER ID   IMAGE                        COMMAND       CREATED          STATUS          PORTS     NAMES
ef27229a41c4   bluenviron/mediamtx:latest   "/mediamtx"   19 seconds ago   Up 18 seconds             goofy_franklin

When I go to publish an MP4 to it via ffmpeg I get connection refused errors:

ffmpeg -re -stream_loop -1 -i fireplace.mp4 -c copy -f rtsp rtsp://localhost:8554/mystream
ffmpeg version 6.0 Copyright (c) 2000-2023 the FFmpeg developers
  built with Apple clang version 14.0.0 (clang-1400.0.29.202)
  configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/6.0_1 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libaribb24 --enable-libbluray --enable-libdav1d --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libsvtav1 --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-audiotoolbox --enable-neon
  libavutil      58.  2.100 / 58.  2.100
  libavcodec     60.  3.100 / 60.  3.100
  libavformat    60.  3.100 / 60.  3.100
  libavdevice    60.  1.100 / 60.  1.100
  libavfilter     9.  3.100 /  9.  3.100
  libswscale      7.  1.100 /  7.  1.100
  libswresample   4. 10.100 /  4. 10.100
  libpostproc    57.  1.100 / 57.  1.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'fireplace.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf59.27.100
  Duration: 00:00:11.27, start: 0.000000, bitrate: 522 kb/s
  Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, smpte170m/bt470bg/smpte170m, progressive), 368x640, 448 kb/s, 30 fps, 30 tbr, 15360 tbn (default)
    Metadata:
      handler_name    : VideoHandler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc59.37.100 libx264
  Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 64 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
      vendor_id       : [0][0][0][0]
[tcp @ 0x13160fbd0] Connection to tcp://localhost:8554?timeout=0 failed: Connection refused
[out#0/rtsp @ 0x13160edd0] Could not write header (incorrect codec parameters ?): Connection refused
[aost#0:1/copy @ 0x13160f720] Error initializing output stream: 
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
    Last message repeated 1 times

Describe how to replicate the issue

1. All instructions provided above

Did you attach the server logs?

no this is via Docker

Did you attach a network dump?

no this is via Docker

I have also asked this on StackOverflow to see if anyone with more Docker knowledge can provide any insight.

[mrlt8]

AFAIK, MacOS/Docker Desktop doesn't support --network=host so you'll need to manually expose the ports:

docker run --rm -it \
-e MTX_PROTOCOLS=tcp \
-p 8554:8554 \
-p 1935:1935 \
-p 8888:8888 \
-p 8889:8889 \
-p 8890:8890/udp \
bluenviron/mediamtx

[bitbythecron]

Thank you for FWIW if anyone else has the same problem I found the answer here on StackOverflow. Basically it was a combination of the (as @mrlt8 alluded) --network=host option interfering with Mac's Docker Desktop, as well as the ffmpeg commands I was using for both publish and read.

[bluenviron-bot]

This discussion is being locked automatically because the last update was more than 2 years ago.

Do not use the content of this discussion as reference since it's probably outdated!

The official documentation is the only place in which you can find up-to-date answers.