containers
Here are 2,626 public repositories matching this topic...
-
Updated
May 7, 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
May 9, 2021 - Shell
currently in https://github.com/medyagh/minikube/blob/a67a4ccbedd932f184b5713c70498dc434942621/pkg/minikube/bootstrapper/images/images.go#L86
we have
// etcd returns the image used for etcd
func etcd(v semver.Version, mirror string) string {
// Should match `DefaultEtcdVersion` in:
// https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/constants/constants.go
ev := "
-
Updated
May 8, 2021 - Go
-
Updated
May 7, 2021 - Rust
Any hover effects doesn't properly applied to all header elements (top line with cluster name and cluster menu). It seems that something placed on top of them and covers most of their height.
https://user-images.githubusercontent.com/9607060/108056014-cd186a00-7061-11eb-8ac0-5d01e206e636.mp4
In what area(s)?
/area test-and-release
Describe the proposal
Currently before each rc release
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
-
Updated
May 9, 2021 - JavaScript
-
Updated
Feb 4, 2021 - Go
Description
While writing a PacketImpact test for ICMP sockets, I found a discrepancy with Linux.
When binding to the following IPv6 multicast addresses,
ff01::1ff02::1ff02::2
Linux returns the EINVAL error code, but gVisor returns the EADDRNOTAVAIL error code.
Steps to reproduce
- Run test `//third_party/gvisor/test/packetimpact/tests:icmp_bind_nati
Change GoogleContainerTools/skaffold#4531 waits for pending resource deletions before attempting to redeploy. This sometimes leads to DEPLOY_ERR_WAITING_FOR_DELETION when the wait for deletion times out. The current default timeout seems to be 2 secs. Could you please increase this default or make it configurable?
As an extension, skaffold could look into not waiting for
-
Updated
Apr 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
May 5, 2021 - Go
-
Updated
Apr 29, 2021 - PHP
-
Updated
Feb 24, 2020 - Go
-
Updated
May 8, 2021 - Go
-
Updated
May 8, 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
May 9, 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
May 9, 2021 - Go
-
Updated
May 5, 2021 - Go
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
May 5, 2021 - TypeScript
-
Updated
May 9, 2021 - Go
-
Updated
May 1, 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: