/area test-and-release
/kind good-first-issue

Describe the feature

When debugging end to end tests locally, it's frequently helpful to keep resources around after the test run finishes to debug things. Currently this requires finding the call to EnsureTearDown and commenting

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

All of our instances are reported as launched on ubuntu-core-18 now, due to strict confinement and base: core18. We should try and find a way to reach out to get the actual host OS.

https://github.com/canonical/multipass/blob/d9a72641a254a0613fe4344aa3cb93a67a6b055b/src/daemon/daemon.cpp#L116-L117

ko publish ./cmd/...
2020/12/19 09:39:01 failed to publish images: found 7 local packages, expected 1

ko resolve is capable of building and deploying multiple images, and ko publish is seemingly capable of identifying multiple import paths to build, but we run afoul of https://github.com/google/ko/blob/722ad3c37b2e01219aa053ba11b6b0d6d065b5d7/pkg/commands/publisher.go#L39 in `ko

PreparingDelete应该是准备原地删除吧

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

MongoDB changed its license to be untenably restrictive.

It’s been more than a year when the upstream MongoDB decided to change the license of the Server code. The previous license was GNU Affero General Public License v3 (AGPLv3). However, upstream wrote a new license designed to make companies running MongoDB as a service contribute back to the community. The new license is called Server Side

Docker enables folks to use custom certs for their registries via this directory (and possibly environment variables). We should figure out how tools can support this, perhaps through support directly in the library, or perhaps through documentation on how to properly set up the http.RoundTripper passed into remote.Foo calls.

crane and ko would be good examples for how we add support f