profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/MHBauer/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Morgan Bauer MHBauer Bay Area, California, USA, Earth mhbauer.com Currently looking for new position. Please check out my work experience! https://mhbauer.com/2021/january/morgan-bauers-work-resume/

docker/docker-credential-helpers 616

Programs to keep Docker login credentials safe by storing in platform keystores

docker/go-connections 146

Utility package to work with network connections

docker/go-units 121

Parse and print size and time units in human-readable format

cloudviz/agentless-system-crawler 105

A tool to crawl systems like crawlers for the web

cloudfoundry-attic/blockhead 3

CF-Extensions Blockhead project

ibm-contribs/kubernetes 2

Fork of Kubernetes for contributions from certain IBMers

pull request commentkubernetes/community

adding question

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/community/pull/5771#" title="Author self-approved">rficcaglia</a> To complete the pull request process, please assign iancoldwater after the PR has been reviewed. You can assign the PR to them by writing /assign @iancoldwater in a comment when ready.

The full list of commands accepted by this bot can be found here.

<details open> Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":["iancoldwater"]} -->

rficcaglia

comment created time in 24 minutes

PR opened kubernetes/community

adding question

and answer after slack discussion 5/7

<!-- Thanks for sending a pull request! Here are some tips for you:

  • If this is your first contribution, read our Getting Started guide https://github.com/kubernetes/community/blob/master/contributors/guide/README.md
  • If you are editing SIG information, please follow these instructions: https://git.k8s.io/community/generator You will need to follow these steps:
    1. Edit sigs.yaml with your change
    2. Generate docs with make generate. To build docs for one sig, run make WHAT=sig-apps generate -->

Which issue(s) this PR fixes: <!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). If PR is about failing-tests or flakes, please post the related issues/tests in a comment and do not use Fixes --> Fixes #

+6 -0

0 comment

1 changed file

pr created time in 25 minutes

pull request commentcontainerd/containerd

Fix `content.ReaderAt` close

It will actually call os.Open, this PR complements this close.

When local is used by the client. There are more use cases I have seen that are trying to use the containerd client directly with a content store. When used through the content service, such as the client, the Close doesn't do anything since the content service automatically closes at the end of a request.

wzshiming

comment created time in an hour

issue commentkubernetes/community

Clarify social media guidelines regarding boosting of non Kubernetes/CNCF events

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

mrbobbytables

comment created time in 2 hours

issue openedcontainerd/containerd

Can not pull docker images from private registry when authentication is activated

I initially created my ticket here https://github.com/k3s-io/k3s/issues/3291 but it seems as it is only related to containerd.

I can not pull images through containerd (v1.4.4-k3s1) as part of the k3s distribution because my private registry (pulp-container) expects the token request as /token/?service=blabla (see https://docs.pulpproject.org/pulp_container/workflows/authentication.html) but containerd seems to send only /token/ according to the logs:

May  8 19:52:44 localhost gunicorn[126347]: pulp [cb2b6fbd57404749a68ff3d28ebb1113]: django.request:WARNING: Bad Request: /token/
May  8 19:52:44 localhost gunicorn[126347]: pulp [cb2b6fbd57404749a68ff3d28ebb1113]: 127.0.0.1 - - [08/May/2021:19:52:44 +0000] "GET /token/ HTTP/1.0" 400 38 "https://pulp.test.com/token" "Go-http-client/1.1"

I tested it with docker and podman. There login and pulling images works normally. It also works if I remove the auth: part in the configuration and pull the images without authentication. But in the future I also want to restrict read access to the registry. Is there maybe a configuration option in containerd where I can specify the ?service=blabla or is this a bug?

I can also reproduce it manually when I just send the requests via curl to the registry server:

curl -I https://pulp.test.com/token/
HTTP/1.1 400 Bad Request

curl -I https://pulp.test.com/token/?service=blabla
HTTP/1.1 200 OK

created time in 3 hours

issue commentdocker/cli

Clarify what an image reference is

The documentation regarding this seems to have improved: https://docs.docker.com/engine/reference/commandline/images/ (there is a section entitled Filter images by reference).

johndmulhausen

comment created time in 4 hours

issue commentIBM/cloud-operators

OperatorHub Version outdated

Thanks for opening @marrau. This is something we made some strides toward, but have not yet completed.

As usual, PRs are welcome 😄

marrau

comment created time in 5 hours

issue commentIBM/cloud-operators

Operator installation script fails to apply 3 yaml files due to missing namespace

@amitsadaphule Thanks for opening. The order yaml files are applied isn't great sometimes. To work around this issue for now, you can retry the installer script multiple times. If a resource is not created on the first pass, a second pass should fix it.

amitsadaphule

comment created time in 5 hours

created repositorydlorenc/go-warden

created time in 7 hours

PR opened orf/cargo-bloat-action

Bump handlebars from 4.7.2 to 4.7.7

Bumps handlebars from 4.7.2 to 4.7.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.7 - February 15th, 2021</h2> <ul> <li>fix weird error in integration tests - eb860c0</li> <li>fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - b6d3de7</li> <li>fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - f058970</li> <li>refactor: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>) - 77825f8</li> <li>chore: start testing on Node.js 12 and 13 - 3789a30</li> </ul> <p>(POSSIBLY) BREAKING CHANGES:</p> <ul> <li>the changes from version <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md#v460---january-8th-2020">4.6.0</a> now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1633">#1633</a> for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.</li> </ul> <p>That is why we only bump the patch version despite mentioning breaking changes.</p> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">Commits</a></p> <h2>v4.7.6 - April 3rd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1672">#1672</a> - Switch cmd parser to latest minimist (<a href="https://api.github.com/users/dougwilson"><code>@​dougwilson</code></a></li> </ul> <p>Compatibility notes:</p> <ul> <li>Restored Node.js compatibility</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.5...v4.7.6">Commits</a></p> <h2>v4.7.5 - April 2nd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><del>Node.js version support has been changed to v6+</del> Reverted in 4.7.6</li> </ul> <p>Compatibility notes:</p> <ul> <li><del>Node.js < v6 is no longer supported</del> Reverted in 4.7.6</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.4...v4.7.5">Commits</a></p> <h2>v4.7.4 - April 1st, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1666">#1666</a> - Replaced minimist with yargs for handlebars CLI (<a href="https://api.github.com/users/aorinevo"><code>@​aorinevo</code></a>, <a href="https://api.github.com/users/AviVahl"><code>@​AviVahl</code></a> & <a href="https://api.github.com/users/fabb"><code>@​fabb</code></a>)</li> </ul> <p>Compatibility notes:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/a9a8e403213583ca90cb7c872d3a22796c37d961"><code>a9a8e40</code></a> v4.7.7</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e66aed5b99c1b6c93564f37d627e34e5d60eb76e"><code>e66aed5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/7d4d170ce46a53084a41920c5c7387c131357989"><code>7d4d170</code></a> disable IE in Saucelabs tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/eb860c08998f8f506360d305d89e1f4b40f72a0a"><code>eb860c0</code></a> fix weird error in integration tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8"><code>b6d3de7</code></a> fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427"><code>f058970</code></a> fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/77825f8d3522356feb8e4160fac16344104d192b"><code>77825f8</code></a> refator: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3789a309554fd600caeae442f40881cf93eb3b54"><code>3789a30</code></a> chore: start testing on Node.js 12 and 13</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e6ad93ea01bcde1f8ddaa4b4ebe572dd616abfaa"><code>e6ad93e</code></a> v4.7.6</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/2bf4fc6fd3ae3d8f076d628653f284d85faebeb4"><code>2bf4fc6</code></a> Update release notes</li> <li>Additional commits viewable in <a href="https://github.com/wycats/handlebars.js/compare/v4.7.2...v4.7.7">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+22 -31

0 comment

1 changed file

pr created time in 9 hours

issue commentcontainerd/containerd

Systemd unit fails to start when `Type=notify` and host is rebooted

This behavior appeared in the release of 1.4.3

joedborg

comment created time in 11 hours

issue openedkubernetes/klog

[]byte will use +%v through InfoS.

/kind bug

What steps did you take and what happened: [A clear and concise description of what the bug is.]

klog.InfoS("[]byte", "b1", []byte("hello world"))

print: I0508 19:35:13.452661 57319 testKlog.go:11] "[]byte" b1=[104 101 108 108 111 32 119 111 114 108 100]

What did you expect to happen: I0508 19:37:01.473191 2045 testKlog.go:11] "[]byte" b1="hello world"

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] part of https://github.com/kubernetes/kubernetes/issues/101714 As k8s conducts structured log migration, InfoSis used more and more, but[]byte, usually cooperates with %q beforethe migration, is it necessary to submit a PR so that []byte uses %q in InfoS? Currently in InfoS, []byte uses %+v. https://github.com/kubernetes/klog/blob/0cc9b8363efc89db73313bf618deeff8964c4a86/klog.go#L832 If the idea is approved, I will do it.

created time in 13 hours

issue commentkubernetes/apimachinery

[Question] How to decode a RawExtension ?

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten

eddycharly

comment created time in 13 hours

issue openeddocker/cli

Allow rootless Docker to keep host UID/GID

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see https://github.com/docker/cli/blob/master/CONTRIBUTING.md#reporting-other-issues


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Docker Community Slack - https://dockr.ly/community
  • Post a question on StackOverflow, using the Docker tag

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->

It's common for certain images (for example, the LinuxServer group's images to start the container as a user with the same UID to avoid permission issues. However, with the user namespace remap in rootless Docker, this no longer works. For example, if I attempt to start a container as a user with UID 1000, it is remapped to 10099.

Currently, Podman provides a feature which allows a rootless container's user to have the same UID/GID as the user starting the container. Would it be possible to implement this for rootless Docker?

A concrete example: When I map a folder from my host into a Docker container, I have to run as root in the container (which I'm not comfortable with) in order to create any files inside the mapped folder. This feature would solve that issue.

created time in 14 hours

issue commentcontainerd/containerd

BTRFS plugin causes high CPU consumption

chart2~2 CPU usage after reducing the sync period to 15 minutes and later to 2 hours.

@dmcstable The kubelet has very little impact on a mostly stable/static cluster. It's just the containerd stats sync.

mar-kolya

comment created time in 16 hours

pull request commentcontainerd/containerd

Sandbox API

I have some questions about that shimv2 api and sandbox api. If we create a sandbox with sandbox api, then the task can run in the sandbox. so if a shimv2 server is started after sanbox started, and serves an endpoint that containerd can connect, then containerd can start task directly through the shimv2 service in the sandbox. I think that would be a better design, because there is no need of a shim on the host for each pod. the shimv2 server can run in the sandbox(for the vm based sandbox, it runs in the vm, and provide service through virtio-vsock or serial port, replacing the agent in the vm, or the agent serves shimv2 api directly).

mxpv

comment created time in 17 hours

issue commentcontainerd/nri

Building the Container Device Interface with NRI

/cc

RenaudWasTaken

comment created time in 18 hours

PR opened atilag/statevector-simulator

Bump url-parse from 1.4.7 to 1.5.1 in /www

Bumps url-parse from 1.4.7 to 1.5.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/unshiftio/url-parse/commit/eb6d9f51e395b7e47bf2594e457d541db21c713b"><code>eb6d9f5</code></a> [dist] 1.5.1</li> <li><a href="https://github.com/unshiftio/url-parse/commit/750d8e8a9d45dbce9ff09759f0fe4564cdd47d74"><code>750d8e8</code></a> [fix] Fixes relative path resolving <a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/199">#199</a> <a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/200">#200</a> (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/201">#201</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/3ac777474ba5dc48a7e33771cbb311fc6f69bef8"><code>3ac7774</code></a> [test] Make test consistent for browser testing</li> <li><a href="https://github.com/unshiftio/url-parse/commit/267a0c6f7ef1a58271be61611c5103daace602c9"><code>267a0c6</code></a> [dist] 1.5.0</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0"><code>d1e7e88</code></a> [security] More backslash fixes (<a href="https://github-redirect.dependabot.com/unshiftio/url-parse/issues/197">#197</a>)</li> <li><a href="https://github.com/unshiftio/url-parse/commit/d99bf4cf259b7378c855f786edc253e70405ffdc"><code>d99bf4c</code></a> [ignore] Remove npm-debug.log from .gitignore</li> <li><a href="https://github.com/unshiftio/url-parse/commit/422c8b5e4cac6a79cd35b4e86731476dcbeec7e4"><code>422c8b5</code></a> [pkg] Replace nyc with c8</li> <li><a href="https://github.com/unshiftio/url-parse/commit/933809d630c7b21399b4e5df59fccccd80033b21"><code>933809d</code></a> [pkg] Move coveralls to dev dependencies</li> <li><a href="https://github.com/unshiftio/url-parse/commit/190b2168035899a2a88f2dc2625963bf7e2f338f"><code>190b216</code></a> [pkg] Add .npmrc</li> <li><a href="https://github.com/unshiftio/url-parse/commit/ce3783f4ea25753cfa36376769c14e4e2fe6ea80"><code>ce3783f</code></a> [test] Do not test on all available versions of Edge and Safari</li> <li>Additional commits viewable in <a href="https://github.com/unshiftio/url-parse/compare/1.4.7...1.5.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

pr created time in 18 hours

issue openeddocker/cli

The option "docker compose up" return 401 status

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see https://github.com/docker/cli/blob/master/CONTRIBUTING.md#reporting-other-issues


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Docker Community Slack - https://dockr.ly/community
  • Post a question on StackOverflow, using the Docker tag

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->

Description

<!-- Briefly describe the problem you are having in a few paragraphs. --> I tried "docker compose up" to start a set of services, which are made from my private images which is managed in my private repository with private registry URL, but I failed. I got a 401 error. When I use the "docker-compose up", everything is OK. Is there a bug?

Steps to reproduce the issue:

  1. make a private docker image server;
  2. use the private image url to write the docker-compose.yml;
  3. run command with option just like "docker compose up" and you get 401!
  4. run command with option just like "docker-compose up" and everything is OK.

Describe the results you received: A 401 ERROR!

Describe the results you expected: I want it to make a set of containers correctly just like what docker-compose does.

Additional information you deem important (e.g. issue happens only occasionally): Here is the log of my operations and the output from docker commands:

PS C:\Users\XXX\XXX\xxx> docker login --username=100012672305 repo_url
Password:
Login Succeeded
PS C:\Users\XXX\XXX\xxx> docker compose up -d
[+] Running 4/4
 - Network "xxx_default"     Created                                                                  0.1s
 - Container xxx_database_1  Started                                                                  1.4s
 - Container xxx_web_1       Started                                                                  1.1s
 - Container xxx_server_1    Started                                                                  1.5s
PS C:\Users\XXX\XXX\xxx> docker compose down
[+] Running 4/4
 - Container xxx_web_1       Removed                                                                  0.7s
 - Container xxx_database_1  Removed                                                                 10.8s
 - Container xxx_server_1    Removed                                                                  0.7s
 - Network "xxx_default"     Removed                                                                  0.2s
PS C:\Users\XXX\XXX\xxx> docker compose up -d
[+] Building 0.9s (9/9) FINISHED
 => [web internal] load build definition from Dockerfile                                                           0.1s
 => => transferring dockerfile: 90B                                                                                0.0s
 => [database internal] load build definition from Dockerfile                                                      0.1s
 => => transferring dockerfile: 89B                                                                                0.0s
 => [server internal] load build definition from Dockerfile                                                        0.1s
 => => transferring dockerfile: 94B                                                                                0.0s
 => [web internal] load .dockerignore                                                                              0.1s
 => => transferring context: 2B                                                                                    0.0s
 => [database internal] load .dockerignore                                                                         0.1s
 => => transferring context: 2B                                                                                    0.0s
 => [server internal] load .dockerignore                                                                           0.1s
 => => transferring context: 2B                                                                                    0.0s
 => ERROR [web internal] load metadata for repo_url/repo_name/xxx_web:latest                 0.4s
 => CANCELED [database internal] load metadata for repo_url/repo_name/xxx_db:latest          0.3s
 => CANCELED [server internal] load metadata for repo_url/repo_name/xxx_service:latest       0.3s
------
 > [web internal] load metadata for repo_url/repo_name/xxx_web:latest:
------
The new 'docker compose' command is currently experimental. To provide feedback or request new features please open issues at https://github.com/docker/compose-cli
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
PS C:\Users\XXX\XXX\xxx> docker-compose up -d
Docker Compose is now in the Docker CLI, try `docker compose up`

Creating network "xxx_default" with the default driver
Pulling database (repo_url/repo_name/xxx_db:)...
latest: Pulling from repo_name/xxx_db
f7ec5a41d630: Already exists
9444bb562699: Already exists
6a4207b96940: Already exists
181cefd361ce: Already exists
8a2090759d8a: Already exists
15f235e0d7ee: Already exists
d870539cd9db: Already exists
cb7af63cbefa: Already exists
151f1721bdbf: Already exists
fcd19c3dd488: Already exists
415af2aa5ddc: Already exists
f736a6aa955b: Already exists
22e11a4f5057: Already exists
73fa1acb7783: Already exists
cb73f05f31cb: Already exists
Digest: sha256:ff8397fe019022f8df4c2c8d2465404a4cf1a83d419a9dd60615a9ab3a1cf06f
Status: Downloaded newer image for repo_url/repo_name/xxx_db:latest
Pulling server (repo_url/repo_name/xxx_service:)...
latest: Pulling from repo_name/xxx_service
ca3cd42a7c95: Already exists
bc9e52c7d177: Already exists
e7cfeb78f743: Already exists
b58f76aa64f4: Already exists
49da6b273c6b: Already exists
08a8e258aaf5: Already exists
84f0e2449889: Already exists
a72c7e4b8176: Already exists
ab6c2ca4b4cf: Already exists
1d07c4936b17: Already exists
a98446eba5de: Already exists
ddb41d962d84: Already exists
4f4fb700ef54: Already exists
a9cbeba2a6b2: Already exists
Digest: sha256:fddec77beb7b90bfabefd9cab4bf7f10a9db1e9ff8906a5eb58e522434c67c21
Status: Downloaded newer image for repo_url/repo_name/xxx_service:latest
Pulling web (repo_url/repo_name/xxx_web:)...
latest: Pulling from repo_name/xxx_web
540db60ca938: Already exists
2b54d6979bcc: Already exists
72b89a422da5: Already exists
2aa15c209059: Already exists
844f0a4f6618: Already exists
4f4fb700ef54: Already exists
fd26b8489f85: Already exists
Digest: sha256:d1e949819b234b909dac8b36f06ea322bf4e7e510d7b517585f26e2b5d05fc80
Status: Downloaded newer image for repo_url/repo_name/xxx_web:latest
Creating xxx_server_1   ... done
Creating xxx_web_1      ... done
Creating xxx_database_1 ... done

Output of docker version:

Client: Docker Engine - Community
 Cloud integration: 1.0.12
 Version:           20.10.5
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        55c4c88
 Built:             Tue Mar  2 20:14:53 2021
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.5
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       363e9a8
  Built:            Tue Mar  2 20:15:47 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  scan: Docker Scan (Docker Inc., v0.6.0)

Server:
 Containers: 8
  Running: 5
  Paused: 0
  Stopped: 3
 Images: 35
 Server Version: 20.10.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2 io.containerd.runtime.v1.linux
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.4.72-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 18.69GiB
 Name: docker-desktop
 ID: BPBS:LAMD:7YTX:WZ35:SDBA:WCRO:34DO:X5D2:PNCY:KLAM:KJ3B:MYSX
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support

Additional environment details (AWS, VirtualBox, physical, etc.):

created time in 19 hours

pull request commentcontainerd/containerd

Fix `content.ReaderAt` close

Build succeeded.

wzshiming

comment created time in 19 hours

pull request commentcontainerd/containerd

Fix `content.ReaderAt` close

Hi @wzshiming. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

<details>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. </details>

wzshiming

comment created time in 20 hours

PR opened containerd/containerd

Fix `content.ReaderAt` close

content.ReaderAt is used in many places but not closed, It will actually call os.Open, this PR complements this close.

https://github.com/containerd/containerd/blob/01ca105b6a7c3d4307fe3d9cd847c7d48519a7bd/content/local/store.go#L128-L141

https://github.com/containerd/containerd/blob/01ca105b6a7c3d4307fe3d9cd847c7d48519a7bd/content/local/readerat.go#L35-L56

+8 -1

0 comment

4 changed files

pr created time in 20 hours

issue openedcontainerd/containerd

Flaky test: TestTrigger in gc/scheduler

Description

TestTrigger failed

Steps to reproduce the issue:

  1. checkout v1.5.0
  2. cd containerd
  3. go test -v -count 100000 ./gc/scheduler -run TestTrigger

Describe the results you received:

...
=== RUN   TestTrigger
--- PASS: TestTrigger (0.00s)
=== RUN   TestTrigger
    scheduler_test.go:135: GC wait timed out
--- FAIL: TestTrigger (0.01s)
...
=== RUN   TestTrigger
--- PASS: TestTrigger (0.00s)
FAIL
FAIL    github.com/containerd/containerd/gc/scheduler   10.209s
FAIL

Describe the results you expected:

The test passed.

What version of containerd are you using:

v1.5.0

<!-- Tips:

  • If containerd gets stuck on something and enables debug socket, ctr pprof goroutines dumps the golang stack of containerd, which is helpful! If containerd runs without debug socket, kill -SIGUSR1 $(pidof containerd) also dumps the stack as well.

  • If there is something about running containerd, like consuming more CPU resources, ctr pprof subcommands will help you to get some useful profiles. Enable debug socket makes life easier. -->

<details><summary><code>runc --version</code></summary><br><pre> $ runc --version runc version 1.0.0-rc93+dev commit: fc8a0d97a9ade7a270114eded52c8c64f037a430 spec: 1.0.2-dev go: go1.16.3 libseccomp: 2.5.1 </pre></details>

<details><summary><code>uname -a</code></summary><br><pre> $ uname -a Linux vultr.guest 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux </pre></details>

created time in 20 hours

PublicEvent

pull request commentcontainerd/containerd

services/introspection: support to show introspection grpc service plugin

@stevvooe @AkihiroSuda PTAL, Thanks

Iceber

comment created time in a day

pull request commentkubernetes/community

Update README.md

@caseydavenport one last lgtm needed ! :)

jayunit100

comment created time in a day

fork martinmaly/blueprints

Sample blueprints for Google Cloud

fork in a day