profile
viewpoint

containers/libpod 4795

libpod is a library used to create container pods. Home of Podman.

docker/docker-credential-helpers 522

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

emojisum/emojisum 227

:pray: :paperclip: Emoji that checksum! :tada: :poop:

containerd/continuity 78

A transport-agnostic, filesystem metadata manifest system

containers/Demos 40

Repository is a location of user demos for technologies listed on github.com/containers

opencontainers/oci-conformance 28

OCI Conformance Working Group

shanemhansen/gossl 27

Go bindings to the openssl library

containers/BuildSourceImage 14

Tool to build a source image based on an existing OCI image

vbatts/bvi 6

binary file editor (history assembled from http://bvi.sourceforge.net/)

vbatts/acme-reverseproxy 5

A multi-domain, TLS, reverse proxy that uses Let's Encrypt (https://letsencrypt.org/) as the automatic CA.

issue commentbazelbuild/bazel

Release 3.3 - June 2020

hrm. Glad I did a build of 3.3.0 first, where only epel7-aarch64 failed (as it has). So far on 3.3.1 it has also failed for fedora31-aarch64 and epel8-aarch64. (other aarch64 targets did succeed). Perhaps a memory constraint? All other targets succeed.

laurentlb

comment created time in 2 days

issue commentbazelbuild/bazel

Release 3.3 - June 2020

https://copr.fedorainfracloud.org/coprs/build/1515066

I totally missed pushing a build for 3.3.0 also, so I did that first

laurentlb

comment created time in 2 days

push eventvbatts/copr-build-bazel

Vincent Batts

commit sha 727f5035331a3f1bcf12f0341470de1ec84b6824

update to 3.3.1 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in 2 days

created tagvbatts/copr-build-bazel

tagv3.3.1-1

copr build of bazel | https://copr.fedorainfracloud.org/coprs/vbatts/bazel/

created time in 2 days

push eventvbatts/copr-build-bazel

Vincent Batts

commit sha 592563c7166408ad65741d95ce6f1dd2ea5ad433

update to 3.3.1 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in 2 days

push eventvbatts/copr-build-bazel

Vincent Batts

commit sha 5be52db7db17afe5c9c5947ea3271e38c71e47c3

bazel 3.3.0 https://github.com/bazelbuild/bazel/releases/tag/3.3.0 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in 2 days

created tagvbatts/copr-build-bazel

tagv3.3.0-1

copr build of bazel | https://copr.fedorainfracloud.org/coprs/vbatts/bazel/

created time in 2 days

push eventvbatts/copr-build-bazel

Vincent Batts

commit sha 9002cb0b0ed3a007de94bbf99f12eedbca2363bf

bazel 3.3.0 https://github.com/bazelbuild/bazel/releases/tag/3.3.0 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in 2 days

pull request commentopencontainers/distribution-spec

extension proposal

This basically needs community discussion around "how can i experiment with bringing in new features, or have my own bespoke feature"

vbatts

comment created time in 3 days

pull request commentopencontainers/distribution-spec

extension proposal

scope of the extensions:

 extensions are meant as a way to extend on the generic basic workflows available in the distribution-spec

A way to have a handshake between client-server for additional features capable. e.g. search, signatures, discoverability. etc

The hope of having a server expose which features it implements vs. a newer version (i.e. /v2/) that implements new features, in synchrony. It's okay to add a batch of OPTIONAL features to the spec, with language around "if you use this OPTIONAL http endpoint then you MUST use the corresponding ones".

I'm really wondering whether this is even the correct approach.

If these features are the right and good for distribution-spec (the API), then just put them in the spec and rev the version.

(Having a call with @dmcgowan @jzelinskie @mikebrow @jdolitsky @vbatts)

vbatts

comment created time in 3 days

Pull request review commentopencontainers/distribution-spec

mini update 4: fill in definitions section

 keywords: registry, on-prem, images, tags, repository, distribution, api, advanc --- # Open Container Initiative -## Distribution Specification+## Table of Contents -This specification defines an API protocol to facilitate distribution of images.+- [Overview](#overview)+	- [Introduction](#introduction)+	- [Historical Context](#historical-context)+	- [Definitions](#defintions)+- [Conformance](#conformance)+	- [Notational Conventions](#notational-conventions)+	- [Minimum Requirements](#minimum-requirements)+	- [Official Certification](#official-certification)+	- [Workflow Categories](#workflow-categories)+		1. [Pull](#pull)+		2. [Push](#push)+		3. [Content Discovery](#content-discovery)+		4. [Content Management](#content-management)+- [HTTP API](#http-api)+	- [Endpoints](#endpoints)+	- [Error Codes](#error-codes) -The goal of this specification is to standardize container image distribution based on the specification for the [Docker Registry HTTP API V2 protocol](https://github.com/docker/distribution/blob/5cb406d511b7b9163bff9b6439072e4892e5ae3b/docs/spec/api.md).+## Overview -### Table of Contents+### Introduction -- [Introduction](spec.md)-- [Notational Conventions](#notational-conventions)-- [Historical Context](#historical-context)-- [Scope](#scope)-  - [Future](#future)-- [Use Cases](#use-cases)-  - [Image Verification](#image-verification)-  - [Resumable Push](#resumable-push)-  - [Resumable Pull](#resumable-pull)-  - [Layer Upload De-duplication](#layer-upload-de-duplication)-- [Changes](#changes)-- [Overview](#overview)-  - [Errors](#errors)-  - [API Version Check](#api-version-check)-  - [Content Digests](#content-digests)-  - [Pulling An Image](#pulling-an-image)-  - [Pushing An Image](#pushing-an-image)-  - [Listing Repositories](#listing-repositories)-  - [Listing Image Tags](#listing-image-tags)-  - [Deleting an Image](#deleting-an-image)-- [Detail](#detail)-  - [Errors](#errors-2)-  - [Base](#base)-  - [Tags](#tags)-  - [Manifest](#manifest)-    - [GET Manifest](#get-manifest)-    - [PUT Manifest](#put-manifest)-    - [DELETE Manifest](#delete-manifest)-  - [Blob](#blob)-    - [GET Blob](#get-blob)-      - [Fetch Blob](#fetch-blob)-      - [Fetch Blob Part](#fetch-blob-part)-    - [DELETE Blob](#delete-blob)-  - [Initiate Blob Upload](#initiate-blob-upload)-    - [POST Initiate Blob Upload](#post-initiate-blob-upload)-      - [Initiate Monolithic Blob Upload](#initiate-monolithic-blob-upload)-      - [Initiate Resumable Blob Upload](#initiate-resumable-blob-upload)-      - [Mount Blob](#mount-blob)-  - [Blob Upload](#blob-upload)-    - [GET Blob Upload](#get-blob-upload)-    - [PATCH Blob Upload](#patch-blob-upload)-    - [PUT Blob Upload](#put-blob-upload)-    - [DELETE Blob Upload](#delete-blob-upload)--## Notational Conventions--The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119) (Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997).--The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the [rationale for the C99 standard][c99-unspecified].--An implementation is not compliant if it fails to satisfy one or more of the MUST, MUST NOT, REQUIRED, SHALL, or SHALL NOT requirements for the protocols it implements.-An implementation is compliant if it satisfies all the MUST, MUST NOT, REQUIRED, SHALL, and SHALL NOT requirements for the protocols it implements.--## Historical Context+The Open Container Initiative Distribution Specification defines an API protocol to facilitate and standardize the distribution of content, especially related to container images and associated artifacts.++### Historical Context++The spec is based on the specification for the [Docker Registry HTTP API V2 protocol](https://github.com/docker/distribution/blob/5cb406d511b7b9163bff9b6439072e4892e5ae3b/docs/spec/api.md).  For relevant details and a history leading up to this specification, please see the following issues:  - [moby/moby#8093](https://github.com/moby/moby/issues/8093) - [moby/moby#9015](https://github.com/moby/moby/issues/9015) - [docker/docker-registry#612](https://github.com/docker/docker-registry/issues/612) -<!--- TODO: add relevant background information here --->+### Definitions++Several terms are used frequently in this document and warrant basic definitions:++- **Registry**: a HTTP service which implements this spec

a service which implements the server side of this spec? because technically the client implements the spec too

jdolitsky

comment created time in 3 days

Pull request review commentopencontainers/distribution-spec

mini update 4: fill in definitions section

 keywords: registry, on-prem, images, tags, repository, distribution, api, advanc --- # Open Container Initiative -## Distribution Specification+## Table of Contents -This specification defines an API protocol to facilitate distribution of images.+- [Overview](#overview)+	- [Introduction](#introduction)+	- [Historical Context](#historical-context)+	- [Definitions](#defintions)+- [Conformance](#conformance)+	- [Notational Conventions](#notational-conventions)+	- [Minimum Requirements](#minimum-requirements)+	- [Official Certification](#official-certification)+	- [Workflow Categories](#workflow-categories)+		1. [Pull](#pull)+		2. [Push](#push)+		3. [Content Discovery](#content-discovery)+		4. [Content Management](#content-management)+- [HTTP API](#http-api)+	- [Endpoints](#endpoints)+	- [Error Codes](#error-codes)

rebase for the prior TOC updates?

jdolitsky

comment created time in 3 days

push eventopencontainers/distribution-spec

jdolitsky

commit sha 04ad275c0d07c47c1d13a0f5eadab61579beadf7

mini update 3: fill in overview section Fill in the overview section, including new introduction referring to "content" (vs. just container images). Move historical context section underneath overview. Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

jdolitsky

commit sha ae7e6fc82d5a7903ff2eb6046f836bc5f9d23847

Merge branch 'mini-update-2' of github.com:bloodorangeio/distribution-spec into HEAD Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

jdolitsky

commit sha 691fa861f580dd20cd523bb71fe7b32c99f6b983

Merge branch 'reorg' of github.com:opencontainers/distribution-spec into mini-update-3 Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

Vincent Batts

commit sha 0206eb65bb0bb267fd8ac25b9e162fa38f0bbd2f

Merge pull request #160 from bloodorangeio/mini-update-3 mini update 3: fill in overview section

view details

push time in 3 days

PR merged opencontainers/distribution-spec

mini update 3: fill in overview section

Fill in the overview section, including new introduction referring to "content" (vs. just container images).

Move historical context section underneath overview.


This PR is built on top of #159, so the diff is misleading. Please see the following for a true diff: https://github.com/bloodorangeio/distribution-spec/compare/mini-update-2...bloodorangeio:mini-update-3

+14 -14

5 comments

1 changed file

jdolitsky

pr closed time in 3 days

pull request commentopencontainers/distribution-spec

mini update 3: fill in overview section

LGTM

jdolitsky

comment created time in 3 days

push eventopencontainers/distribution-spec

jdolitsky

commit sha 7cb2fb5d011625a47b1eaea9771bd6a134fe78a3

mini update 1: remove reorg comment It seemed like a good idea at first to reorganize things in a giant HTML comment, but it appears a failed strategy. Instead, going to piecemeal changes into spec.md itself, on the "reorg" branch. Then when everything ready, we can make a big PR from "reorg" onto "master". Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

jdolitsky

commit sha c85806385e307fa10dc800d16b0789c32405cc56

mini update 2: new table of contents This is a new table of contents for the spec, designed to add simplicity and organization. Existing content will later be moved into one of these sections, or removed entirely if considered superfluous. Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

jdolitsky

commit sha 108dc9b7abcd91b9ec6f3527f9bda348fc22600d

Merge branch 'reorg' of github.com:opencontainers/distribution-spec into HEAD Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

jdolitsky

commit sha 0190a3b44071c200df14f1906cbccc2f556bc7c2

remove top-level defintions section Signed-off-by: jdolitsky <393494+jdolitsky@users.noreply.github.com>

view details

Vincent Batts

commit sha 5d0af1c003814a315d31a696783598c882cde223

Merge pull request #159 from bloodorangeio/mini-update-2 mini update 2: new table of contents

view details

push time in 3 days

PR merged opencontainers/distribution-spec

mini update 2: new table of contents

This is a new table of contents for the spec, designed to add simplicity and organization.

Existing content will later be moved into one of these sections, or removed entirely if considered superfluous.


This PR is built on top of #158, so the diff is misleading. Please see the following for a true diff: https://github.com/bloodorangeio/distribution-spec/compare/mini-update-1...bloodorangeio:mini-update-2

+15 -42

4 comments

1 changed file

jdolitsky

pr closed time in 3 days

Pull request review commentopencontainers/distribution-spec

mini update 2: new table of contents

 The goal of this specification is to standardize container image distribution ba  ### Table of Contents -- [Introduction](spec.md)-- [Notational Conventions](#notational-conventions)-- [Historical Context](#historical-context)-- [Scope](#scope)-  - [Future](#future)-- [Use Cases](#use-cases)-  - [Image Verification](#image-verification)-  - [Resumable Push](#resumable-push)-  - [Resumable Pull](#resumable-pull)-  - [Layer Upload De-duplication](#layer-upload-de-duplication)-- [Changes](#changes) - [Overview](#overview)-  - [Errors](#errors)-  - [API Version Check](#api-version-check)-  - [Content Digests](#content-digests)-  - [Pulling An Image](#pulling-an-image)-  - [Pushing An Image](#pushing-an-image)-  - [Listing Repositories](#listing-repositories)-  - [Listing Image Tags](#listing-image-tags)-  - [Deleting an Image](#deleting-an-image)-- [Detail](#detail)-  - [Errors](#errors-2)-  - [Base](#base)-  - [Tags](#tags)-  - [Manifest](#manifest)-    - [GET Manifest](#get-manifest)-    - [PUT Manifest](#put-manifest)-    - [DELETE Manifest](#delete-manifest)-  - [Blob](#blob)-    - [GET Blob](#get-blob)-      - [Fetch Blob](#fetch-blob)-      - [Fetch Blob Part](#fetch-blob-part)-    - [DELETE Blob](#delete-blob)-  - [Initiate Blob Upload](#initiate-blob-upload)-    - [POST Initiate Blob Upload](#post-initiate-blob-upload)-      - [Initiate Monolithic Blob Upload](#initiate-monolithic-blob-upload)-      - [Initiate Resumable Blob Upload](#initiate-resumable-blob-upload)-      - [Mount Blob](#mount-blob)-  - [Blob Upload](#blob-upload)-    - [GET Blob Upload](#get-blob-upload)-    - [PATCH Blob Upload](#patch-blob-upload)-    - [PUT Blob Upload](#put-blob-upload)-    - [DELETE Blob Upload](#delete-blob-upload)+	- [Introduction](#introduction)

is the indentation messed up?

jdolitsky

comment created time in 3 days

Pull request review commentopencontainers/distribution-spec

Add registry proxying section

 If the image had already been deleted or did not exist, a `404 Not Found` respon  > for more details, see: [compatibility.md](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#backward-compatibility) +### Registry Proxying++A registry MAY operate as a proxy to another registry to support pull-through caching or proxying of pull operations (such as fetching tags, manifests, or blobs).+In this case, the `Host` header passed to the proxy registry WILL NOT be the same as the host in the repository name used by the client.+A `ns` query parameter on pull operations is OPTIONAL, but when used specifies the host in a repository name used by a client.+This host component in a repository name SHOULD be the registry host a client considers the primary source for a repository, however, a client MAY be configured to use a different host.+The host in the repository name SHOULD be the first component of the full repository name used by a client.+This original host component used by the client is referred to as the source host in the API documentation.+A proxy registry MAY use the `ns` query parameter to resolve an upstream registry host.+A proxy registry MAY choose to ignore the `ns` query parameter.++A client SHOULD be aware of whether a registry host is being used is a proxy.

http headers that the client SHOULD log somewhere?

dmcgowan

comment created time in 6 days

pull request commentflatcar-linux/coreos-overlay

etcd: update URL to its own org on github now

oh! Apologies. Thank you dongsu.

On Fri, Jun 26, 2020, 10:09 Dongsu Park notifications@github.com wrote:

I have cherry-picked this PR to beta, alpha, and edge. FYI, usually the person who merges a PR should care about the cherry-picks. ;-)

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/flatcar-linux/coreos-overlay/pull/445#issuecomment-650199612, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQL2OJDC6CO4J2I7HWB6TRYSTXVANCNFSM4OITUP2A .

vbatts

comment created time in 6 days

delete branch flatcar-linux/coreos-overlay

delete branch : vbatts/etcd

delete time in 6 days

push eventflatcar-linux/coreos-overlay

Vincent Batts

commit sha 2cbf08b7ab2eafa96cbc1d1112171faaca22e633

etcd: update URL to it's own org on github now even though they're still building from quay.io/coreos/etcd? maybe that'll change soon too? Signed-off-by: Vincent Batts <vbatts@kinvolk.io>

view details

Vincent Batts

commit sha 1256e5038ac2cd55800c60060fb2f0908b9e3b47

Merge pull request #445 from flatcar-linux/vbatts/etcd etcd: update URL to its own org on github now

view details

push time in 6 days

PR merged flatcar-linux/coreos-overlay

etcd: update URL to its own org on github now

even though they're still building from quay.io/coreos/etcd? maybe that'll change soon too?

Signed-off-by: Vincent Batts vbatts@kinvolk.io

[Title: describe the change in one sentence]

etcd has been promoted to its own org now

How to use

click the links

Testing done

Tested that the new links work. (and that the quay.io/coreos/etcd are still correct as well)

+2 -2

0 comment

2 changed files

vbatts

pr closed time in 6 days

PR opened flatcar-linux/coreos-overlay

etcd: update URL to its own org on github now

even though they're still building from quay.io/coreos/etcd? maybe that'll change soon too?

Signed-off-by: Vincent Batts vbatts@kinvolk.io

[Title: describe the change in one sentence]

etcd has been promoted to its own org now

How to use

click the links

Testing done

Tested that the new links work. (and that the quay.io/coreos/etcd are still correct as well)

+2 -2

0 comment

2 changed files

pr created time in 7 days

create barnchflatcar-linux/coreos-overlay

branch : vbatts/etcd

created branch time in 7 days

push eventvbatts/varnish-cache

push time in 7 days

push eventvbatts/varnish-cache

Vincent Batts

commit sha b7499e273f4624b5a320427f5b7061dd1f9f3417

rebasing 0007-revert-grace-hits-hit-for-pass-objs.patch https://github.com/wikimedia/operations-debs-varnish4/blob/8ede97abd894d19308184309b8b8306960d1f3cd/debian/patches/0007-revert-grace-hits-hit-for-pass-objs.patch

view details

push time in 7 days

issue commentkinvolk/nebraska

RFE: OIDC login for support

PRs can be easier, but when it is super involved, like a refactor or relies on other features, then PRs can be painful. That's when it's fruitful to propose and discuss first. Something like this could be incremental.

On Wed, Jun 24, 2020, 19:18 Albert Lloveras notifications@github.com wrote:

Thanks for clarifying that @vbatts https://github.com/vbatts.

I haven't had much time to look deeper into the current authentication model. I will have a deeper look and try to write an implementation proposal.

Is that how you guys expect people to propose new changes or you prefer people to send PRs directly?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kinvolk/nebraska/issues/220#issuecomment-649122700, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQL2JNSCYJDRKVSRABXHTRYKCT3ANCNFSM4NS5YK4A .

vbatts

comment created time in 8 days

delete tag vbatts/go-mtree

delete tag : 0.2.2

delete time in 8 days

issue commentvbatts/go-mtree

The option of specifying the option `-f` twice is not implemented

That would be valuable. And that is how the BSD version reads. Hrm.

Current flag parser we use doesn't support multiple flags, but I've mulled on switching to a different cli backend like cobra or urfave/cli.

zachawilson

comment created time in 9 days

issue commentpackethost/cluster-api-provider-packet

Provisioning fails with "invalid character '#' looking for beginning of value"

I think there are two (or more) ways to go about this issue:

  • Add support for something like ignition, as opposed to hardcoded cloudinit
  • Flatcar cloudinit is a compatible implementation in golang (not the upstream python one), so we could add a fix to ignore this setting (I don't like this option. Hacky, but most accessible)
  • Add a way to override or extend this cloudinit content via the Cluster/machine spec

-------- Original Message -------- On Jun 17, 2020, 12:56, Jason DeTiberus wrote:

We added that when we started using the jinja templating functionality in newer versions of cloud-init based on the cloud-init docs here: https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data

Based on the docs I linked, if ## jinja-template is not the first line, then the functionality will not be enabled.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

dongsupark

comment created time in 10 days

delete branch flatcar-linux/ignition

delete branch : vbatts/rebase-vultr

delete time in 10 days

push eventflatcar-linux/ignition

Vincent Batts

commit sha 818c3936ad4589628e3aa58020138d4573eb9ae5

oem: Add Vultr as a provider * added vultr to oem reg * Fix bad endpoint Co-authored-by: Mike Biondi <biondizzle@gmail.com> Co-authored-by: eb3095 <45504889+eb3095@users.noreply.github.com> Signed-off-by: Vincent Batts <vbatts@kinvolk.io>

view details

Vincent Batts

commit sha d27259c85d746504c5dfbaca1e3d2bc816b2a6e9

Merge pull request #13 from flatcar-linux/vbatts/rebase-vultr oem: Add Vultr as a provider

view details

push time in 10 days

PR merged flatcar-linux/ignition

oem: Add Vultr as a provider
  • added vultr to oem reg

cc @eb3095 ref https://github.com/eb3095/ignition/pull/2

Co-authored-by: Mike Biondi biondizzle@gmail.com Co-authored-by: eb3095 45504889+eb3095@users.noreply.github.com Signed-off-by: Vincent Batts vbatts@kinvolk.io

oem: Add Vultr as a provider

How to use

./bin/amd64/ignition -oem vultr ...

Testing done

Have not

+52 -0

2 comments

2 changed files

vbatts

pr closed time in 10 days

pull request commentflatcar-linux/ignition

oem: Add Vultr as a provider

:+1:

vbatts

comment created time in 10 days

issue commentkinvolk/nebraska

RFE: OIDC login for support

@alloveras I don't think it is blocking the work on any OIDC feature here. I'm referring to standing up a kinvolk managed accounts, so users can identify their nebraska instance to kinvolk.

vbatts

comment created time in 10 days

issue commentcontainerd/cri

Add user namespace support

@mikebrow more-or-less I did :smile_cat: . I was a conversation to see what the next step needed will be, and the answer was a KEP.

Random-Liu

comment created time in 13 days

CommitCommentEvent

issue commentflatcar-linux/Flatcar

Kernel Sources not loading in Developmental Container

@rikatz like @pothos mentioned with the docs link, I recently did similar to get a flatcar stable machine to have wireguard modules https://gist.github.com/vbatts/9af92a341611751dc3a157f204a84973

kshitizbakshi

comment created time in 16 days

pull request commentdeislabs/oras

Proposal to add Vincent Batts as a maintainer of ORAS

On 10/06/20 18:33 -0700, Steve Lasker wrote:

Welcome [1]@vbatts

ohman

SteveLasker

comment created time in 21 days

delete branch kinvolk/lokomotive

delete branch : vbatts/correct_iago_key

delete time in 22 days

push eventkinvolk/lokomotive

Vincent Batts

commit sha 7a3c01049dbeef9dc5822ba68472211b43090f6f

keys: iago's key is kinvolk.io, not gmail 🤓 Signed-off-by: Vincent Batts <vbatts@kinvolk.io>

view details

push time in 22 days

PR opened kinvolk/lokomotive

Reviewers
keys: iago's key is kinvolk.io, not gmail 🤓

Signed-off-by: Vincent Batts vbatts@hashbangbash.com

+2 -2

0 comment

1 changed file

pr created time in 22 days

create barnchkinvolk/lokomotive

branch : vbatts/correct_iago_key

created branch time in 22 days

issue commentkubernetes/enhancements

KEP: Enhance the KEP implementation

Right on!

justaugustus

comment created time in 23 days

issue commentkubernetes/enhancements

KEP: Enhance the KEP implementation

Looking over the points, it looks like much of this is done. (Perhaps checkboxes could be clearer) Would this graduate the KEP process from beta?

justaugustus

comment created time in 23 days

pull request commentappc/docker2aci

Statically link objects

:+1:

sanmai-NL

comment created time in 23 days

pull request commentmpolden/echoip

http: enable getting json from another IP

@mpolden that is a good idea. And I'm wondering if this is an ability to have a flag on the server for. Since you manage the online service and domain, it could be more utilized. I'm willing to run this on my local instance, since only I abuse that one :-D

vbatts

comment created time in 24 days

issue commentflatcar-linux/locksmith

Migrate to Go modules

@dmlambea nice. Be sure to rebase on the main branch. Some of the import paths were touched in #2. Also some of the changes like the 'object' field may best be a separate PR. But please feel free to open PRs non-the-less.

invidian

comment created time in 24 days

delete branch flatcar-linux/docs

delete branch : vbatts/01

delete time in 24 days

pull request commentopencontainers/tob

projects: add ORAS proposal

apart from the maintainer balance, :+1:

jdolitsky

comment created time in a month

Pull request review commentopencontainers/tob

projects: add ORAS proposal

+# OCI ORAS Project Proposal #++## Abstract ##++The [ORAS project][oras-project] is a CLI that can publish arbitrary content to an OCI registry, with special features for setting mediatypes on manifest configs and on content. ++In order to provide OCI end users a method to publish and retrieve any type of content to/from an OCI registry, as well as a reference implementation for the in-progress artifacts spec, ORAS should be moved under the opencontainers GitHub org.++[oras-project]: https://github.com/deislabs/oras++### ORAS Details ###++ORAS is a CLI that can publish arbitrary content to an OCI registry, with special features for setting mediatypes on manifest configs and on content.++Note: the manifest mediatype itself is always `application/vnd.oci.image.manifest.v1+json`.++Example - uploading rockets, a brand new type of package:++```+# Create a thing+printf '🚀' > rocket.txt++# Create a manifest config+printf '{"RocketVersion":"v0.1.0"}' > rocket-config.json++# Upload your thing with a custom mediatype+oras push localhost:5000/mystuff/myrocket:v0.1.0 rocket.txt:text/plain \+  --manifest-config rocket-config.json:application/vnd.acme.rocket.config.v1+json+ ```++See manifest created:++```+$ curl -s -H 'Accept: application/vnd.oci.image.manifest.v1+json' \+    http://localhost:5000/v2/mystuff/myrocket/manifests/v0.1.0 | jq+{+  "schemaVersion": 2,+  "config": {+    "mediaType": "application/vnd.acme.rocket.config.v1+json",+    "digest": "sha256:310175f34d2d4d5cba3418be06ddd1ef948147d729516d78318ec7f5c2d83d49",+    "size": 26+  },+  "layers": [+    {+      "mediaType": "text/plain",+      "digest": "sha256:ebbc0b2870eb323f2b6cffa5c493ceef81ae7eb36afc73d4e0367301631daec5",+      "size": 4,+      "annotations": {+        "org.opencontainers.image.title": "rocket.txt"+      }+    }+  ]+}+```++Get that thing:++```+$ curl -s http://localhost:5000/v2/mystuff/myrocket/blobs/sha256:ebbc0b2870eb323f2b6cffa5c493ceef81ae7eb36afc73d4e0367301631daec5+🚀+```++#### Additional Usage ####++ORAS is built primarily on top of Go packages provided by [containerd][containerd-project], but it also imports packages from the [docker/cli][dockercli-project], which enables "docker-style" auth login:++```+oras login -u username -p password localhost:5000 -c rocket-creds.json+```++There are also public Go packages available to build on top of ORAS. The following is the equivalent of the rocket example with the CLI above, but in Go:++```go+package main++import (+	"context"+	"fmt"++	"github.com/containerd/containerd/remotes/docker"+	"github.com/deislabs/oras/pkg/content"+	"github.com/deislabs/oras/pkg/oras"+	ocispec "github.com/opencontainers/image-spec/specs-go/v1"+)++func main() {+	ctx := context.Background()+	resolver := docker.NewResolver(docker.ResolverOptions{})+	store := content.NewMemoryStore()++	registryRootURL := "localhost:5000"+	registryNamespace := "mystuff/myrocket"++	rocketVersion := "v0.1.0"+	rocketFileName := "rocket.txt"+	rocketMediaType := "text/plain"+	rocketContent := []byte("🚀")+	rocketDescriptor := store.Add(rocketFileName, rocketMediaType, rocketContent)++	rocketConfigMediaType := "application/vnd.acme.rocket.config.v1+json"+	rocketConfigContent := []byte(fmt.Sprintf("{\"RocketVersion\":\"%s\"}", rocketVersion))+	rocketConfigDescriptor := store.Add("", rocketConfigMediaType, rocketConfigContent)++	ref := fmt.Sprintf("%s/%s:%s", registryRootURL, registryNamespace, rocketVersion)+	_, err := oras.Push(ctx, resolver, ref, store, []ocispec.Descriptor{rocketDescriptor},+		oras.WithConfig(rocketConfigDescriptor))+	if err != nil {+		panic(err)+	}++	fmt.Println("Pushed to", ref)+	fmt.Printf("\nTry:\n\ncurl -s -H 'Accept: application/vnd.oci.image.manifest.v1+json' \\\n" ++		"    %s/v2/%s/manifests/%s | jq\n", registryRootURL, registryNamespace, rocketVersion)+}+```++You can see all features in the project [README][oras-readme].++[containerd-project]: https://github.com/containerd/containerd+[dockercli-project]: https://github.com/docker/cli+[oras-readme]: https://github.com/deislabs/oras/blob/master/README.md++#### Adoption ####++The following projects are already successfully using ORAS to work with custom artifacts:++- [Helm][helm-usage]+- [Conftest][conftest-usage]+- [Singularity][singularity-usage]++[helm-usage]: https://github.com/helm/helm/search?q=oras+[conftest-usage]: https://github.com/instrumenta/conftest/search?q=oras+[singularity-usage]: https://github.com/sylabs/singularity/search?q=oras++## Proposal ##+Change the ownership of the existing ORAS project from deislabs:++  https://github.com/deislabs/oras++And move it inside the `opencontainers` organization:++  https://github.com/opencontainers/oras++The import paths will correspondingly be "github.com/opencontainers/oras" (oras does have some Go API users, but since the project will be renamed -- and GitHub will add a redirect -- there will be no significant downstream impact of the change).++### Initial Maintainers ###+Initial maintainers of the ORAS project would be:

A) This may be too many folks from a single employer B) I could participate here

jdolitsky

comment created time in a month

pull request commentopencontainers/tob

projects: add umoci proposal

:+1:

cyphar

comment created time in a month

delete branch opencontainers/tob

delete branch : simplify-mission-statement

delete time in a month

push eventopencontainers/tob

Chris Aniszczyk

commit sha ec2cda22eeddbae4f80f4163e381160dfc6017cc

Simplify mission of OCI to reflect reality Signed-off-by: Chris Aniszczyk <caniszczyk@linuxfoundation.org>>

view details

Vincent Batts

commit sha 8ddbb7928335a5aca3d82c7f9ead3009842f7706

Merge pull request #77 from opencontainers/simplify-mission-statement Simplify mission of OCI

view details

push time in a month

PR merged opencontainers/tob

Simplify mission of OCI

Based on feedback from @samuelkarp

Signed-off-by: Chris Aniszczyk caniszczyk@linuxfoundation.org

+3 -12

9 comments

1 changed file

caniszczyk

pr closed time in a month

pull request commentopencontainers/tob

Simplify mission of OCI

LGTM

caniszczyk

comment created time in a month

issue openedkinvolk/nebraska

RFE: OIDC login for support

A feature for users to have available logging in for support assistance. This would rely on services that are not finished yet, but would make for a smooth user experience for those managing an update-service.

created time in a month

issue commentbazelbuild/bazel

Release 3.2 - May 2020

I welcome any testing that folks offer here :-D

laurentlb

comment created time in a month

push eventvbatts/copr-build-bazel

Vincent Batts

commit sha c0a0745b6d37f426f1e963880025bbbfea059ce5

update to 3.2.0 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

created tagvbatts/copr-build-bazel

tagv3.2.0-1

copr build of bazel | https://copr.fedorainfracloud.org/coprs/vbatts/bazel/

created time in a month

push eventvbatts/copr-build-bazel

Vincent Batts

commit sha c0a0745b6d37f426f1e963880025bbbfea059ce5

update to 3.2.0 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

issue commentbazelbuild/bazel

Release 3.2 - May 2020

late to the party, but fedora and centos are built https://copr.fedorainfracloud.org/coprs/vbatts/bazel/build/1424821/ Still epel-7-aarch64 failed, but all the rest succeeded.

laurentlb

comment created time in a month

pull request commentmpolden/echoip

http: enable getting json from another IP

@mpolden thoughts for the direction of this PR?

vbatts

comment created time in a month

issue commentkinvolk/inspektor-gadget

Create a contribution guide

:+1: would be good to lean on a consistent base for contribution guidelines. /cc @joaquimrocha

mauriciovasquezbernal

comment created time in a month

push eventvbatts/utils

Vincent Batts

commit sha 01fc4d4fed8db283d33af3d2aec49d1f8af7350b

see-pr: update README Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

startedkubernetes/security

started time in a month

issue openedkubernetes/security

private-distributors-list: add Kinvolk

<!-- Please answer the following questions and provide supporting evidence for meeting the membership criteria. -->

Actively monitored security email alias for our project: security@kinvolk.io

1. Be an actively maintained and CNCF certified distribution of Kubernetes components. https://github.com/cncf/k8s-conformance/pull/959#issuecomment-626046888

2. Have a user base not limited to your own organization. Lokomotive has open-source users, as well as supported users.

3. Have a publicly verifiable track record up to present day of fixing security issues. This is still early, but releases on https://github.com/kinvolk/lokomotive

4. Not be a downstream or rebuild of another distribution. Lokomotive has its roots from https://github.com/poseidon/typhoon and still a good relationship, but had differing goals so it fully diverged last year. Works with upstream otherwise.

5. Be a participant and active contributor in the community. https://github.com/iaguis https://github.com/alban https://github.com/surajssd

6. Accept the Embargo Policy. <!-- https://github.com/kubernetes/security/blob/master/private-distributors-list.md#embargo-policy --> yes

7. Be willing to contribute back. <!-- Per https://github.com/kubernetes/security/blob/master/private-distributors-list.md#contributing-back --> yes

8. Have someone already on the list vouch for the person requesting membership on behalf of your distribution. Not yet, I will work on this next

created time in a month

startedkinvolk/lokomotive

started time in a month

push eventvbatts/utils

Vincent Batts

commit sha f774e31cc1146639ead2aadc8b7720d3e9983ea8

see-pr: to add the github PR pull refspec Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

push eventvbatts/utils

Vincent Batts

commit sha 3f578370c94b457612c5ac445dba4958616454c8

see-pr: to add the github PR pull refspec Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

push eventvbatts/utils

Vincent Batts

commit sha e8c0a9d2e5d6c9ef16c05c67b9e9733797e74d64

LICENSE: add an MIT license Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

pull request commentopencontainers/distribution-spec

Spec reorganization pt 1

ohman. Heavy weight champ over here!

jdolitsky

comment created time in a month

pull request commentflatcar-linux/seismograph

Fix setting the label

Oh nice. Good catch.

pothos

comment created time in a month

push eventflatcar-linux/ignition

Vincent Batts

commit sha 818c3936ad4589628e3aa58020138d4573eb9ae5

oem: Add Vultr as a provider * added vultr to oem reg * Fix bad endpoint Co-authored-by: Mike Biondi <biondizzle@gmail.com> Co-authored-by: eb3095 <45504889+eb3095@users.noreply.github.com> Signed-off-by: Vincent Batts <vbatts@kinvolk.io>

view details

push time in a month

PR opened flatcar-linux/ignition

oem: Add Vultr as a provider
  • added vultr to oem reg

cc @eb3095 ref https://github.com/eb3095/ignition/pull/2

Co-authored-by: Mike Biondi biondizzle@gmail.com Co-authored-by: eb3095 45504889+eb3095@users.noreply.github.com Signed-off-by: Vincent Batts vbatts@kinvolk.io

oem: Add Vultr as a provider

How to use

./bin/amd64/ignition -oem vultr ...

Testing done

Have not

+52 -0

0 comment

2 changed files

pr created time in a month

create barnchflatcar-linux/ignition

branch : vbatts/rebase-vultr

created branch time in a month

pull request commentopencontainers/runtime-spec

MAINTAINERS: Add @cyphar as maintainer

with a 4/6 vote

giuseppe

comment created time in a month

push eventopencontainers/runtime-spec

Giuseppe Scrivano

commit sha d759f35237a78422aaef3aa49d548798ba1c5266

MAINTAINERS: Add @cyphar as maintainer Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>

view details

Vincent Batts

commit sha 237cc4f519e2e8f9b235bacccfa8ef5a84df2875

Merge pull request #1043 from giuseppe/add-cyphar-to-MAINTAINERS MAINTAINERS: Add @cyphar as maintainer

view details

push time in a month

PR merged opencontainers/runtime-spec

MAINTAINERS: Add @cyphar as maintainer

I propose Aleksa Sarai (@cyphar) to be added to the runtime-spec maintainers.

Signed-off-by: Giuseppe Scrivano gscrivan@redhat.com

+1 -0

7 comments

1 changed file

giuseppe

pr closed time in a month

pull request commentopencontainers/runtime-spec

MAINTAINERS: Add @cyphar as maintainer

LGTM

giuseppe

comment created time in a month

issue commentkubernetes-sigs/bootkube

Can no longer execute "make vendor"

What to do with generating the license-bill-of-material?

invidian

comment created time in a month

delete branch flatcar-linux/docs

delete branch : vbatts/02

delete time in a month

push eventflatcar-linux/docs

Vincent Batts

commit sha c5f5cdbd9caf51362c7a50538c643ce705abfc26

os: flatcar name and shell cleanup Signed-off-by: Vincent Batts <vbatts@kinvolk.io>

view details

Vincent Batts

commit sha bd03c6bcf1665a13d483c7806552195a5d0a3aef

Merge pull request #89 from flatcar-linux/vbatts/02 os: flatcar name and shell cleanup

view details

push time in a month

PR merged flatcar-linux/docs

os: flatcar name and shell cleanup

Signed-off-by: Vincent Batts vbatts@kinvolk.io

flatcar name and shell cleanup

overly pedantic shell cleanup and new path

How to use

a flatcar instance

Testing done

walked through the examples.

+7 -7

2 comments

1 changed file

vbatts

pr closed time in a month

push eventvbatts/me

Vincent Batts

commit sha fcbb9a00bc12fc718692aa3b7dc1d8ce6f31289c

README: update bio Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>

view details

push time in a month

issue commentflatcar-linux/Flatcar

Kernel Sources not loading in Developmental Container

hah. I just found my way here while working through the docs https://github.com/flatcar-linux/docs/pull/89#issuecomment-630440874

kshitizbakshi

comment created time in a month

pull request commentflatcar-linux/docs

os: flatcar name and shell cleanup

it appears since there are coreos.com URLs posted in the make.conf for PORTAGE_BINHOST=, this command is attempting to get that binary build.

vbatts

comment created time in a month

pull request commentflatcar-linux/docs

os: flatcar name and shell cleanup

edited because the flatcar-sources also has the 404, but no overlays

vbatts

comment created time in a month

push eventflatcar-linux/docs

Vincent Batts

commit sha c5f5cdbd9caf51362c7a50538c643ce705abfc26

os: flatcar name and shell cleanup Signed-off-by: Vincent Batts <vbatts@kinvolk.io>

view details

push time in a month

PR opened flatcar-linux/docs

os: flatcar name and shell cleanup

Signed-off-by: Vincent Batts vbatts@kinvolk.io

flatcar name and shell cleanup

what started as overly pedantic shell cleanup, resulted in fixing the example to be a working flatcar example

How to use

a flatcar instance

Testing done

walked through the examples. with the coreos-sources:

flatcardevelopercontainer ~ # emerge -gKv coreos-sources


!!! Error fetching binhost package info from 'http://builds.developer.core-os.net/boards/amd64-usr/2345.3.1/pkgs/'
!!! HTTP Error 404: Not Found



!!! Error fetching binhost package info from 'http://builds.developer.core-os.net/boards/amd64-usr/2345.3.1/toolchain/'
!!! HTTP Error 404: Not Found
+8 -8

0 comment

1 changed file

pr created time in a month

create barnchflatcar-linux/docs

branch : vbatts/02

created branch time in a month

PR opened flatcar-linux/mantle

kola: force rkt to use docker API for quay

Ref: https://github.com/flatcar-linux/Flatcar/issues/121

Signed-off-by: Vincent Batts vbatts@kinvolk.io

kola: force rkt to use docker API for quay

I don't want --insecure-options= to live on here, but rather test the places that rkt fetches from quay.io

How to use

run the kola tests

Testing done

Not done yet. I'm still learning this area.

+2 -2

0 comment

2 changed files

pr created time in 2 months

create barnchflatcar-linux/mantle

branch : vbatts/rkt-quay

created branch time in 2 months

issue openedflatcar-linux/Flatcar

switch rkt from ACI fetch to docker:// fetch from quay.io

Description

@josephschorr let me know that quay.io intends to deprecate the API for the ACI conversation (ASAP)

Impact

the affects a few places, namely https://github.com/flatcar-linux/mantle/, but likely other places as well.

This does not have to be as invasive as switching from rkt to docker, but just forcing rkt to pull using the docker registry API. (maybe even just prefix the image name with docker://)

created time in 2 months

pull request commentbazelbuild/bazel

Update install-redhat.md for bazel3 package

this change matches up with the instructions I have on https://copr.fedorainfracloud.org/coprs/vbatts/bazel/ to accommodate the major version bumps of the project. :+1:

jiridanek

comment created time in 2 months

PR opened mpolden/echoip

http: enable getting json from another IP

This commit is a slight departure from the perspective of getting information only about the caller's ip, but now allows to get information from arbitrary IPs.

$ ip=$(dig another.example.com | grep ^[[:alpha:]] | awk '{ print $5 }')
$ curl -sSL myechoip.example.com/ip/$ip
{"ip":"172.217.15.78","ip_decimal":2899906382,"country":"United States","country_iso":"US","country_eu":false,"latitude":37.751,"longitude":-97.822,"time_zone":"America/Chicago","hostname":"iad23s63-in-f14.1e100.net"}

Signed-off-by: Vincent Batts vbatts@hashbangbash.com

+45 -8

0 comment

1 changed file

pr created time in 2 months

create barnchvbatts/echoip

branch : ip-check

created branch time in 2 months

fork vbatts/echoip

IP address lookup service

https://ifconfig.co

fork in 2 months

more