Skip to content

umoci 0.4.2
Compare
Choose a tag to compare
@cyphar cyphar released this 11 Sep 03:32
v0.4.2
This tag was signed with the committer’s verified signature.
cyphar Aleksa Sarai
GPG key ID: 9E18AA267DDB8DB4
Learn about vigilant mode.
0975904
This commit was signed with the committer’s verified signature.
cyphar Aleksa Sarai
GPG key ID: 9E18AA267DDB8DB4
Learn about vigilant mode.
  • umoci now has an exposed Go API. At the moment it's unclear whether it will
    be changed significantly, but at the least now users can use
    umoci-as-a-library in a fairly sane way. openSUSE/umoci#245
  • Added umoci unpack --keep-dirlinks (in the same vein as rsync's flag with
    the same name) which allows layers that contain entries which have a symlink
    as a path component. openSUSE/umoci#246
  • umoci insert now supports whiteouts in two significant ways. You can use
    --whiteout to "insert" a deletion of a given path, while you can use
    --opaque to replace a directory by adding an opaque whiteout (the default
    behaviour causes the old and new directories to be merged).
    openSUSE/umoci#257
  • Docker has changed how they handle whiteouts for non-existent files. The
    specification is loose on this (and in umoci we've always been liberal with
    whiteout generation -- to avoid cases where someone was confused we didn't
    have a whiteout for every entry). But now that they have deviated from the
    spec, in the interest of playing nice, we can just follow their new
    restriction (even though it is not supported by the spec). This also makes
    our layers slightly smaller. openSUSE/umoci#254
  • umoci unpack now no longer erases system.nfs4_acl and also has some more
    sophisticated handling of forbidden xattrs. openSUSE/umoci#252
    openSUSE/umoci#248
  • umoci unpack now appears to work correctly on SELinux-enabled systems
    (previously we had various issues where umoci wouldn't like it when it was
    trying to ensure the filesystem was reproducibly generated and SELinux xattrs
    would act strangely). To fix this, now umoci unpack will only cause errors
    if it has been asked to change a forbidden xattr to a value different than
    it's current on-disk value. openSUSE/umoci#235 openSUSE/umoci#259

Thanks to all of the people that made this release possible:

Signed-off-by: Aleksa Sarai asarai@suse.de

Assets 7
Loading