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

As mentioned in the Kubernetes seccomp graduation KEP, it would be helpful to separate the default seccomp profile based on the use runtime class: kubernetes/enhancements#2413 (comment)

We could think about adding such a feature if we decide to not modify the RuntimeClass object in Kubernetes.

What would you like to be added:

We can enrich the following subcommand by adding some details about the next update. For example, current db version, next db version, released datetime, is compatible, digest, etc.

$ grype db check
Update available!

Why is this needed:

For better UX and knowledge.

Additional context:

Recently, we got some bugs and errors related to docker and podman. We have to support those two at least. Incorporating testing into CI could help solve this problem.

How?

I'd like to introduce the run command test on this issue. Perhaps docker is not possible on github actions. It is a good idea to start with podman. Ideally I would like to integrate it into ourown integration tests

What would you like to be added: Add support for markdown tables to be an output format.

Why is this needed: Would allow for easier automated self-documentation without having to rely on external tooling to manipulate the outputs.

Additional context:
The format would behavior similarly to these applications output functionality.

https://github.com/terraform-docs/terraform-do

weaveworks/footloose#259

if using one of the GitHub dark themes, it is near impossible to view documentation images such as

https://github.com/firecracker-microvm/firecracker-containerd/blob/main/docs/img/design-overview.png

and

https://github.com/firecracker-microvm/firecracker-containerd/blob/main/docs/img/design-sequence-diagram.png

due to their usage of black text and transparent background.

It would b

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