containers
Here are 2,534 public repositories matching this topic...
-
Updated
Mar 3, 2021 - Go
Feature idea summary
Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.
-
Updated
Mar 2, 2021 - Shell
The error on this line links to a dead resource: https://docs.doInfo.com/engine/install/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities
-
Updated
Mar 3, 2021 - Go
-
Updated
Mar 3, 2021 - Rust
Describe the bug
When selecting "Help" -> "Documentation" Lens navigates to https://docs.k8slens.dev/ but should navigate to the documentation corresponding to the running version (e.g. https://docs.k8slens.dev/v4.1.0/).
1. Describe IN DETAIL the feature/behavior/change you would like to see.
Using AWS GovCloud is a bit different from the regular AWS.
https://github.com/kubernetes/kops/blob/master/docs/getting_started/aws.md
2. Feel free to provide a design supporting your feature request.
Kops v1.18.2 improves the support for AWS GovCloud and should work without any additional tweaks, except for
-
Updated
Jan 28, 2021 - JavaScript
In what area(s)?
/area test-and-release
Describe the proposal
Add /assign feature to dapr-bot workflow
-
Updated
Feb 4, 2021 - Go
Currently validating checksums requires lots of knowledge on the part of the caller. We should expose optional checksum validation in our existing validation functions e.g. IPv4.IsValid.
header.UDP and header.TCP don't currently have these functions; we should add them.
This is a request for implementing the --post-render flag in helm to be able to execute things like:
helm install mychart stable/wordpress --post-renderer ./path/to/executable
In particular the aim is to use kustomize as a followup of the helm.
Expected behavior
a key to be added to the helm's deploy
Actual behavior
No such option
Information
- Skaffold version: NA
-
Updated
Feb 7, 2021 - Dockerfile
Just like there was an issue to make the jib.to.tags and jib.to.auth to be lazyly evaluated I would need to have the container.labels do the same. Even the reason is the same. I use com.gorylenko.gradle-git-properties Gradle plugin and would like to reuse its properties to add labels to my images. Something like that:
jib {
container {
labels = [
'org.label-schema.
-
Updated
Mar 2, 2021 - Go
-
Updated
Dec 30, 2020 - PHP
-
Updated
Feb 24, 2020 - Go
-
Updated
Mar 3, 2021 - Go
-
Updated
Mar 3, 2021 - Go
-
Updated
Mar 3, 2021 - Go
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
## Python/Regex fix
This is a reminder for me or a task if anyone wants :P
Basically, The last two questions aren't really regex's questions.
To do:
- Move said questions to correct place.
- Add new regex questions (Python related!)?
- Maybe add a new ## Regex section, as it is a valuable skill
-
Updated
Mar 3, 2021 - Go
-
Updated
Mar 2, 2021 - Go
-
Updated
Feb 20, 2021 - TypeScript
-
Updated
Feb 20, 2021 - Go
-
Updated
Feb 25, 2021 - Shell
Currently, Trivy traverses all paths and looks for all Gemfile.lock in a container image. However, the image sometimes has only Gemfile.lock and doesn't install gems listed in the Gemfile.lock. I think a gem should have *.gemspec file if it is installed. e.g. rake.gemspec has the information about rake.
To avoid false positives from Gemfile.lock, we are probably able to take advantage of `*
Improve this page
Add a description, image, and links to the containers topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the containers topic, visit your repo's landing page and select "manage topics."

Inspired by #98726
There are a lot of tests (pkg/apis/networking/validation/validation_test.go in that PR) that have tables of structures like Service or NetworkPolicy, where the struct has to be complete enough (e.g. to pass validation) but each test-case only modifies one tiny section of the otherwise boilerplate struct.
The result is a LOT of noise which makes the actual differences hard