oci

From tcsetpgrp(3):

If tcsetpgrp() is called by a member of a background process group in its session, and the calling process is not blocking or ignoring SIGTTOU, a SIGTTOU signal is sent to all members of this background process group.

Environment:

• Jib version: 2.7.1
• Build tool: Maven
• OS: N/A

Description of the issue:

Invoking mvn jib:help results in error

[ERROR] Could not find goal 'help' in plugin com.google.cloud.tools:jib-maven-plugin:2.7.1 among available goals _skaffold-fail-if-jib-out-of-date, _skaffold-files-v2, _skaffold-init, _skaffold-package-goals, _skaffold-sync-map, build, 

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

right now, there are like 5 different places that need updating if we add a new config/cli field:
pkg/config/config.go to add it to the structure
pkg/config/template.go to add it to the man page template
internal/criocli/criocli.go to add the cli flag
docs/* and completions/* to add completions and documentation

Ideally, we could have just one (or maybe two) places we add a structure, and t

weaveworks/footloose#259

This issue is for tracking the implementation of cgroups v2.
Since cpu and cpuset of cgoups has already been implemented, you can implement it while referring to it.
If you are interested, you can comment on this issue and I will assign it to you.

• cpu containers/youki#48
• cpuset https://github.com/co

Today, Grype can access OCI registries, but only via HTTPS (with a few explicit exceptions made by the go-containerregistry library).

Request: Grype should allow a configuration option to let the user direct Grype to allow the HTTP scheme (as opposed to HTTPS) when co

To repro the issue use an image that is not fully qualified as seen below.

 1 ❯ oras push test:test .
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
github.com/deislabs/oras/vendor/github.com/containerd/containerd/reference.Spec.Hostname(0xc000022bb0, 0x9, 0x0, 0x0, 0x147b544, 0xc0001db788)
...

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