wmf | library supports reading and writing WMF files

Your image is 4-channels of 32-bits each. PIL doesn’t support such images - see Available Modes here.

I would suggest tifffile or OpenCV’s cv2.imread(…, cv2.IMREAD_UNCHANGED)

You're using a pre-warmed image

It seams PIL and crop has some problems with LZW compression. Removing the compression with Photoshop makes the script running like expected.

Updated Answer

You are in luck! GraphicsMagick can do it on alpine:latest:

Use SAX - it will let you cope with the huge file size.

The concept of a "file" is simply some data which belongs to some metadata and that metadata includes a file name and might also include some other stuff like permissions and time stamps.

A file by itself does usually not contain any information about mime types, but its file name might include an extension which might give a hint (right or wrong) about the file content.

Mime types is rather a concept used when a web server sends data to a web client to tell the client how the data should be used. The data that the server sends to a client might be taken from a file or dynamically generated by the web server.

I'm not sure there is a way exactly built in, but if not seems easy to do yourself.

Is this not viable?

The problem turned out to be with ImageMagick's system-wide policy.xml that was installed in my container. Updating that file with more generous "memory" and "disk" values fixed this problem.

You can find the location of your system's policy.xml file using the command convert -list policy (Hat tip to Kurt Pfeifle's answer which clued me in on this). For me it was at /etc/ImageMagick-6/policy.xml. You can edit that file (if you have root access). In the end I decided just to delete the file since I don't want my system from restricting my use at all inside the container.

You can set limits via the command line, say convert -limit memory 2GiB ... or environment variables (See Kurt Pfeifle's answer for details). However, this method does not allow expanding larger than system-wide limits set in policy.xml because this policy file is meant to be a way for system administrators to forcibly limit users. Therefore, the only way to remedy this is to update/remove the system-wide policy.

As you've discovered yourself, it was the presence of machine-level environment variable __PSLockDownPolicy that prevented Install-Module from running (see below for general prerequisites).

This undocumented environment variable, effective on Windows only, is for security reasons only respected if defined at the machine level via the registry (rather than as a per-user or process-specific variable) and can be used to restrict what is allowed in a PowerShell session.

Values 4 through 7 result in PowerShell operating in constrained language mode, where only a handful of pre-approved .NET types may be used, which as a result prevents the PowerShellGet module that contains the Install-Module from loading - see the conceptual about_Language Modes help topic.

You can check what language mode is in effect in a given session by executing $ExecutionContext.SessionState.LanguageMode; in constrained mode, the result is ConstrainedLanguage; FullLanguage indicates that no language restrictions are in place.

Looking at PowerShell's source code, the fact that this variable is checked inside a method named GetDebugLockdownPolicy() suggests that it isn't officially supported.

For more information, see this archived blog post.

The simplest way to remove this restriction is to delete the environment variable, by running the following from an elevated PowerShell prompt: