oci

Now that we have the checklocks analyzer, we should annotate values that are lock-protected with an appropriate checklocks attribute.

Maybe new warnings after upgrading ErrorProne in #3355.

/home/runner/work/jib/jib/jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:250: warning: [UnrecognisedJavadocTag] This Javadoc tag wasn't recognised by the parser. Is it malformed somehow, perhaps with mismatched braces?
58

59
   * Converts a map of volumes strings to a set of {@link Absolut

There are a lot of places in libcontainer/cgroups/fs where the usage of writeFile function can be optimised. For example here https://github.com/opencontainers/runc/blob/master/libcontainer/cgroups/fs/blkio.go#L44-L51
the function call to writeFile is made for each entry in the slice BlkioWeightDevice, which in turn opens and closes file for each entry. This can be optimised by joining al

As per #56 , we are porting the OCI validation tests into rust. This is the tracking issue for the same.
The folder /youki_integration_test contains the currently implemented tests which are lifecyle, creation and huge_tlb

Default

List of all test, as per https://github.com/opencontainers/runtime-tools/tree/master/validation :

• config_updates_without_affect(@WormOn)
• create
• [

weaveworks/footloose#259

Our current documentation for using templates points users to the JSON output to learn about what data is available to the template author. This is insufficient, because although it currently describes the correct shape of data, it leaves users guessing at the correct casing for field names.

A better source of truth than the JSON output is the

It would be ideal to be able to identify and catalog Nix packages.

Repro Steps

Follow steps from: https://github.com/oras-project/artifacts-spec/blob/main/docs/quick-start.md

At the oras discover step, note the output is:

oras discover $PUBLIC_IMAGE -o json | jq
{
  "digest": "sha256:a0fc570a245b09ed752c42d600ee3bb5b4f77bbd70d8898780b7ab43454530eb",
  "references": [
    {
      "digest": "sha256:6200e3cfb0a036bdc585f99cee2ace9926f327d58

In a use case of inserting primarily binary or already compressed objects, having a flag to just disable compression seems feasible.
This would leave the mediaType as just application/vnd.oci.image.layer.v1.tar