You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contrast release v0.7.0 contains a bug that prevents starting containers that contain non-ASCII symbolic link names.
Symptom
The symptom for this is that pods are crashlooping with the following message (indicating a failed policy check):
Error: failed to create containerd task: failed to create shim task: "CreateContainerRequest is blocked by policy [...]
Root Cause
The container image layer tarballs are directly mounted as block devices to the guest VM with the tardev-snapshotter. These devices are verified with a dm-verity checksum that's precalculated by contrast generate (specifically, by the embedded genpolicy tool). The precalculation also involves creating an index over the files in the tarball, which mirrors the index created by the snapshotter.
Microsoft's genpolicy tool contains a fix for long link names, which also happens to be triggered by UTF-8 symlink names due to some canonicalization step. The resulting index is different from what the tardev-snapshotter produces, and thus the dm-verity hashes do not match.
Contrast release
v0.7.0
contains a bug that prevents starting containers that contain non-ASCII symbolic link names.Symptom
The symptom for this is that pods are crashlooping with the following message (indicating a failed policy check):
Root Cause
The container image layer tarballs are directly mounted as block devices to the guest VM with the
tardev-snapshotter
. These devices are verified with adm-verity
checksum that's precalculated bycontrast generate
(specifically, by the embeddedgenpolicy
tool). The precalculation also involves creating an index over the files in the tarball, which mirrors the index created by the snapshotter.Microsoft's
genpolicy
tool contains a fix for long link names, which also happens to be triggered by UTF-8 symlink names due to some canonicalization step. The resulting index is different from what thetardev-snapshotter
produces, and thus the dm-verity hashes do not match.Example Deployment
Problematic symlink:
The text was updated successfully, but these errors were encountered: