containers
Here are 2,599 public repositories matching this topic...
-
Updated
Apr 21, 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
Apr 22, 2021 - Shell
Hi, I am using minikube v1.18.1 on Hyper-V (Microsoft Windows 10 Enterprise)
I recently tried to uninstall minikube and reinstall it.
Steps to reproduce the issue:
- I remove the .minikube directory manually (I know I shouldn’t have), only one file remain : a snapshot file .vmcx, probably the configuration file of my previous VM.
- I added a new Hyper-V switch under the "virtual
-
Updated
Apr 22, 2021 - Go
-
Updated
Apr 21, 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/).
One of the AWS China regions now supports Route53: https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-route-53-is-now-available-in-AWS-china-region/
If someone with an AWS China account can try creating a cluster using Route53 rather than gossip k8s.local and update docs/aws-china.md with their findings that would be much appreciated. Also identify any changes needed to be made in Kops t
In what area(s)?
/area test-and-release
Describe the proposal
Currently before each rc release
-
Updated
Mar 29, 2021 - JavaScript
-
Updated
Feb 4, 2021 - Go
Description
runsc install is able to edit /etc/docker/daemon.json to enable Docker to replace runc with runsc.
Would be great if podman supports this feature.
Is this feature related to a specific bug?
No. By the way, does gVisor depend on Docker just for the reason that Docker uses runsc as its runtime?
Do you have a specific solution in mind?
To replace the runtim
The container-debug-support images uses skaffold build to build and test images. These builds don't have a cluster available and so a plain skaffold build causes Skaffold to attempt to build and push images, which fails. So we explicitly configure build.local.push: false so that the images are only built to the local Docker daemon.
-
Updated
Mar 29, 2021 - Dockerfile
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
-
Updated
Apr 15, 2021 - Go
-
Updated
Mar 30, 2021 - PHP
-
Updated
Feb 24, 2020 - Go
-
Updated
Apr 22, 2021 - Go
-
Updated
Apr 22, 2021 - Go
## 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
Apr 22, 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
-
Updated
Apr 22, 2021 - Go
-
Updated
Apr 22, 2021 - Go
-
Updated
Apr 13, 2021 - TypeScript
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 `*
-
Updated
Apr 22, 2021 - Go
-
Updated
Apr 19, 2021 - Shell
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."

What happened:
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#list-deployment-v1-apps