containers

What would you like to be added?

The changes to support snapshot tests for Generic Ephemeral Volumes kubernetes/kubernetes#105659 generated some duplicated code in the file test/e2e/storage/testsuites/snapshottable.go as commented here: kubernetes/kubernetes#105659 (comment), it'd be great to create functions that are reused in b

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

this info can come handy

and we can also warn ppl with very old vbox to update them

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

What would you like to be added:
A button or link from the list of instances of

In what area(s)?

/area runtime

What version of Dapr?

Runtime 1.5.1, 1.4.3

Expected Behavior

1. Method invocation with URL that contains a urlencoded / character that is %2F:
   http://localhost:[DAPR_PORT]/v1.0/invoke/[MY_SERVICE]/method/test/value%2F123
2. Expected ASP.Core service endpoint to be called from the sidecar:
   /test/value%2F123

Actual Behavior

1. Describe IN DETAIL the feature/behavior/change you would like to see.

Implement WarmPool.RenderTerraform()

2. Feel free to provide a design supporting your feature request.

/kind feature
/area terraform
/lifecycle frozen

kubectl apply -f doesn't check file extensions and we shouldn't either.
https://github.com/GoogleContainerTools/skaffold/blob/9f56bbd6b90128c984d6fb6191dec948fc25822c/pkg/skaffold/kubernetes/util.go#L55-L63

Expected behavior

The following should work:

skaffold render --output m && skaffold apply m

Actual behavior

m is not a valid Kubernetes manifest

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

Right now the main app passes the debug flag to the sensor as a startup param when the global --debug flag is enabled. The --debug flag is a shortcut for the debug log-level configured with the --log-level global flag.

We need to pass the log level param to the sensor when we configure the entrypoint/cmd fields for the temporary container.

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

Description

we have NPM7 generated package-lock.json with lockFileVersion = 2. Now when we scan Node.js project using Trivy filesystem scan, Trivy does not find out packages from package-lock.json.
It is working with lockFileVersion = 1

What did you expect to happen?

It should find out packages in package-lock.json

What happened instead?

It did not find out packages from pack

Hi

I assumed kaniko would work with an on-premise blob store using Azurite Blob Storage, but it looks like it's tied to the Cloud Azure Blob Storage domain name

Would it be difficult to support this? It should be the same API.

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