Description

While writing a PacketImpact test for ICMP sockets, I found a discrepancy with Linux.

When binding to the following IPv6 multicast addresses,

• ff01::1
• ff02::1
• ff02::2

Linux returns the EINVAL error code, but gVisor returns the EADDRNOTAVAIL error code.

Steps to reproduce

1. Run test `//third_party/gvisor/test/packetimpact/tests:icmp_bind_nati

Environment:

• Jib version: 3.0.0
• Build tool: maven 3.6.3,Java version: 1.8.0_282,
• OS: ubuntu20.04

Description of the issue:
mvn clean compile jib:build not work for war project.
have to package the war project. mvn clean package jib:build
The documents and the log output do not mention that.

Expected behavior:
work as jar project.

**Steps to re

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

Issue #14 describes the initial matchers needed. This ticket should be picked up once all those are in place, to extend further:

• pacman
• poetry
• pipenv
• yarn

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