To run a pre-recorded video as an always-on YouTube Live stream with Docker, run FFmpeg in a container, pace the video in real time, and send it to the ingest endpoint and stream key shown in YouTube Live Control Room. Docker packages and runs the encoder; it does not supply power, internet access, or automatic recovery from every failure. The host must stay on and connected, and you must monitor both FFmpeg and YouTube’s stream health.
How the Docker-to-YouTube setup works
The basic path is video file → FFmpeg → YouTube ingest → live broadcast. FFmpeg reads and paces the recording, then either passes through compatible streams or encodes them for delivery. Docker isolates and runs that process. YouTube treats the incoming ingest stream and the viewer-facing broadcast as related but distinct objects, with their own configuration and status information; see the YouTube LiveStreams API reference.
A Docker container can be running while the video is stalled, the network is unavailable, the key is invalid, or YouTube reports an unhealthy stream. The pattern is supported by this Docker and FFmpeg implementation guide, but exact commands depend on your media, FFmpeg build, and output protocol. The example below is therefore a configuration pattern, not a tested, copy-and-run command.
Prepare YouTube and protect the stream key
- Enable live streaming for your channel and create or select the broadcast in YouTube Live Control Room. Channel eligibility and any setup steps are shown in YouTube Studio.
- Get the ingest details from the selected stream configuration. Use the server URL and stream key YouTube actually displays; do not rely on an old endpoint copied from a tutorial. YouTube’s encoder settings guidance recommends RTMPS for a conventional encoder workflow.
- Keep the key secret. Do not commit it to a repository, publish it in a Docker Compose file, include it in a command transcript, or leave it in accessible logs. Anyone who obtains it may be able to send video to your ingest. If it is exposed, replace or rotate it in YouTube’s stream settings and update the container’s secret.
- Make the video readable by the container. Store it on the host and mount its directory read-only, or use a Docker volume. Verify that the path inside the container matches the path FFmpeg will open.
Choose RTMPS or HLS
RTMPS: the straightforward default
YouTube describes RTMPS as a secure extension of RTMP and recommends it; its guidance says data is encrypted in transit into and through Google’s servers. For a typical FFmpeg-to-YouTube workflow, use the RTMPS URL supplied by YouTube with the key handled privately. See the RTMPS ingestion documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
HLS: use it when your workflow needs it
YouTube also supports HLS ingest, but it imposes packaging requirements. Its HLS ingestion guide specifies M2TS, H.264 or HEVC video, AAC audio, closed GOPs, and up to 60 fps. HLS is segment-based and usually has higher latency than RTMP and WebRTC. It is not a general quality upgrade; choose it for workflow compatibility, not an assumed improvement in picture quality.
Set up the container and FFmpeg process
- Select a maintained FFmpeg container image. Pin a specific image version or digest rather than relying on a moving tag, and confirm it includes the required protocol and codec support. Image names and tags change; the sources here do not establish a current tag to recommend.
- Mount the media. For example, map a host media directory to a container directory as read-only, then reference the in-container filename. Keep configuration and secret handling separate from the media mount.
- Configure FFmpeg to play in real time. A file must be paced at playback speed; otherwise an encoder may send it as fast as it can read it. For a repeating playlist or single-file loop, configure the input or supervising process to repeat deliberately. Do not assume that a completed file or ended YouTube broadcast will automatically restart itself.
- Choose pass-through or transcoding. If the source codecs, resolution, frame rate, timestamps, and audio are suitable for YouTube ingest, stream-copy may avoid unnecessary encoding. Otherwise transcode to a supported format and settings. The correct flags depend on the source file and selected protocol, so inspect the media and validate the output rather than copying flags blindly.
- Send to the current YouTube ingest URL. Use RTMPS for the usual simple setup. Inject the stream key through a secret mechanism or protected runtime environment, not a public configuration file. Avoid posting complete commands or logs if they contain the key.
- Keep the host available. Docker runs on a host, so a home computer, server, or rented VM must remain powered, connected, and able to upload continuously. A restart policy can restart an exited container, but it cannot fix a bad key, insufficient bandwidth, invalid media, or YouTube-side health problems.
Looping and the meaning of “always-on”
For uninterrupted playback, the process must repeat the file or advance through a playlist without leaving an unintended gap. The container must also survive process exits, and the broadcast must remain active on YouTube. These are separate conditions: an FFmpeg loop does not itself guarantee that YouTube will keep a broadcast open after an ingest interruption or broadcast end. Configure and verify the encoder behavior and the broadcast lifecycle you need.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Match YouTube’s encoder settings
Use YouTube’s current encoder settings and resolution-specific bitrate table rather than treating one bitrate as suitable for every stream. The page recommends constant bitrate (CBR), a two-second keyframe interval (not more than four seconds), and up to 60 fps. It lists H.264, H.265/HEVC, and AV1 video, and AAC or MP3 audio, with codec-specific constraints. YouTube transcodes live streams into viewer output formats.
- Resolution and frame rate: Choose a mode your source supports and your host can encode if transcoding is needed. A higher source resolution or frame rate increases processing and upload demands.
- Bitrate: Select the value for the chosen resolution and frame rate from YouTube’s current table, then leave upload headroom. A connection that only just matches the video bitrate can become unstable when other devices or traffic compete for capacity.
- Keyframes: Set a two-second interval where the encoder exposes that option, and do not exceed YouTube’s stated four-second maximum.
- Audio: Check that the source has an audio stream in a format accepted by the selected workflow. Silent video can be intentional, but missing or invalid audio can otherwise cause unexpected output or health warnings.
- Test before relying on it: YouTube recommends a test stream with similar audio and motion before the intended broadcast. Monitor stream health during that test.
Launch and verify the live stream
- Start the container with the media mounted and the stream key supplied privately.
- Check container output with
docker logs -f <container-name>. Confirm FFmpeg opens the intended input, advances timestamps, and continues writing output without repeated errors. Ensure displayed logs do not reveal the stream key. - Open YouTube Live Control Room for the selected broadcast. Confirm that YouTube receives video and audio and reports healthy stream status; a running container alone is not proof that viewers are receiving a valid stream.
- Open the public watch page or an unlisted test broadcast and verify that playback is actually live, with the expected picture and sound.
- Keep monitoring the process and YouTube health after launch. Configure a Docker restart policy and external monitoring as appropriate, while recognizing that process restarts do not repair configuration, media, network, or ingest-health faults.
Troubleshoot common failures
| Symptom | Likely cause | What to check or do |
|---|---|---|
| Container exits immediately | FFmpeg command error, missing file, wrong in-container path, or unavailable codec/protocol support. | Inspect container logs, confirm the bind mount and filename, and verify the image’s FFmpeg capabilities. Correct the command or image before enabling restart loops. |
| Container runs but YouTube receives no video | Wrong ingest URL or key, output protocol mismatch, or FFmpeg not producing valid media. | Compare the destination with the current YouTube stream configuration, check FFmpeg output logs, and confirm YouTube’s incoming-stream status. Rotate the key if it may have been exposed. |
| Stream health is poor or intermittent | Upload capacity, network interruptions, or encoding settings that the host cannot sustain. | Check YouTube’s health indicator, test the connection and host load, reduce resolution or bitrate if necessary, and use YouTube’s matching bitrate guidance with upload headroom. |
| Video plays too fast or stops at the end | The input is not paced in real time or looping was not configured. | Configure real-time playback and an explicit repeat or playlist mechanism. Separately confirm the YouTube broadcast remains active as intended. |
| FFmpeg restarts but the broadcast does not recover | A container restart only restarts the process; YouTube broadcast state or ingest health may require separate attention. | Check the Live Control Room’s stream and broadcast status, then reconnect or reconfigure according to the state shown there. Do not treat Docker’s restart policy as YouTube recovery. |
| Audio or video is rejected or missing | Unsupported codec/container packaging, absent audio, or settings incompatible with the selected ingest protocol. | Inspect the input streams and compare the output format with YouTube’s encoder or protocol-specific documentation; for HLS, follow its packaging requirements. |
Or let it run in the cloud
If you want the pre-recorded YouTube stream without maintaining a Docker host, StreamNeo runs uploaded videos from the cloud: upload a recording or build a playlist, add your YouTube stream key once, and go live. Nothing has to stay on at home. Every slot streams the upload as made, up to 4K 60fps, at one price per slot; it also includes 24/7 looping and playlists, 10 GB storage per slot pooled across active slots, and automatic recovery if YouTube drops the stream. The first day is free with no card (one free day per account). Monthly pricing is $9.99 per month.
Quick Recap
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Start your free StreamNeo day.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
