ffmpeg doesn't work from inside a container, but works on the host RRS feed

  • Question

  • Using TP3.

    host> ffmpeg --help

    prints all switches

    container> ffmpeg --help

    [blank line]

    container> echo %ERRORLEVEL%


    This error level corresponds to 64bit/32bit dll mismatches (according to some googling) 

    Any ideas?

    Thanks in advance.

    Wednesday, October 21, 2015 1:06 PM

All replies

  • Hi LevH, 

    I have the same issue recently.

    After some try and errors, I found avicap32.dll and msvfw32.dll, dependency of ffmpeg, are missing in container.

    They are in C:\Windows\System32\ (64bit) or C:\Windows\SysWOW64 (32bit)

    Just copy them from host to container. ffmpeg can work again.


    My environment:

    Host: Windows Server 2016 RTM

    Container: microsoft/windowsservercore:10.0.14393.321


    • Proposed as answer by Xied75 Thursday, October 27, 2016 11:18 AM
    Wednesday, October 26, 2016 1:36 PM
  • Some pages say that AVICAP32.DLL is a part of Video for Windows, which is nowadays installed as part of Desktop-Experience.

    However I've failed to install it in containers too:

    PS> import-module servermanager
    PS> Install-WindowsFeature Desktop-Experience

    Install-WindowsFeature : ArgumentNotValid: The role, role service, or feature name is not valid: 'Desktop-Experience'. The name was not found.

    Image: windowsservercore:10.0.14393.1770

    I wonder what is the right way of installing Video for Windows into containers. Copying .dlls seems to be too hacky way.

    Wednesday, November 15, 2017 3:47 PM