This cumbersome also hit my work.Īfter some trial and error, I found a stable and concise way to hedge this problem. Because of this character, you may suffer you cannot build your image with the package manager. However, unlike ~nix environments, Windows applications do not guarantee they will return exit code zero even if they have any errors.

So I want to utilize the package manager inside the Windows container too. You can obtain many open-source-based Windows command-line tools on the brand-new community-driven package managers such as the Chocolatey package manager. Install Chocolatey Package Manager on the Windows Container You can change your base image name from server core to server almost all tags will match your existing version scheme. The base image called ‘WindowsServer’ consistently solves this problem. That means you cannot pull the base ‘Windows’ image with the tag ‘ltsc2022.’ Instead, you will have to choose the tag ‘20H2,’ which follows the client-side version scheme. But, this image does not fit release cadence with existing nano server and server core images. In this case, we should consider using the ‘Windows’ base image, which has a complete set of APIs. However, it’s a shame that the Windows Version of FFMPEG requires desktop APIs to run its function, and the server core container image does not have the APIs. You may think if the container can handle these multimedia workloads, it will be an excellent service to many users and companies.

Starting Windows Server 2022, Microsoft has released a new kind of base image called ‘WindowsServer.’ The ‘WindowsServer’ base image is the same as the existing base image called ‘Windows’ but designed for the Windows Server-specific feature sets and its release cadence.įFmpeg is a cross-platform multimedia transcoding software that can handle various audio, video, and image formats.

Run ffmpeg linux