Skip to content
#

containers

Here are 2,596 public repositories matching this topic...

wzshiming
wzshiming commented Apr 12, 2021
grep -nr '/enhancements/keps/' * | grep -v '^vendor' | grep -v '/README.md' | grep -v '.json' | grep -v '.pb.go' | grep -v '.proto' | grep -v 'generated'
netdata
loic-rgt
loic-rgt commented Apr 1, 2021

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:

  1. 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.
  2. I added a new Hyper-V switch under the "virtual
lens
rifelpet
rifelpet commented May 18, 2020

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

gvisor
unknowndev233
unknowndev233 commented Jun 23, 2020

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

briandealwis
briandealwis commented Apr 12, 2021

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.

eisig
eisig commented Apr 16, 2021

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

devops-exercises
surister
surister commented Jan 21, 2020

This is a reminder for me or a task if anyone wants :P

imagen

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
fristonio
fristonio commented Aug 22, 2019

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

knqyf263
knqyf263 commented Oct 19, 2020

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.

Curate this topic

Add this topic to your repo

To associate your repository with the containers topic, visit your repo's landing page and select "manage topics."

Learn more