pierone icon indicating copy to clipboard operation
pierone copied to clipboard

STUPS' Docker registry with S3 backend, immutable tags and SCM source tracking

Results 12 pierone issues
Sort by recently updated
recently updated
newest added

Hi team, thanks for all your open source work. Is this Pier One project still active? https://github.com/zalando-stups/pierone/pull/160#issuecomment-395561417 suggests that there is a replacement? We would like to pull spilo images...

I could not find a way of getting the Docker client to use auth for push, but no-auth for pull :disappointed:

bug

This adds support for responding to `HEAD /v2///manifests/` requests. This is required by containerd and described in the opencontainers spec: https://github.com/opencontainers/distribution-spec/blob/master/spec.md#existing-manifests Reference: https://github.com/containerd/cri/issues/787 I need this to pull skipper in...

Since Clair-SQS integration can be disabled, we should not expose any statuses when it's off.

Hi, I did not test at all, but these are current versions.

in progress

Using default configuration, but could not start system ``` $ docker run -it -p 8080:8080 --net=host stups/pierone:1.8.5 INFO [main] o.e.j.u.log - Logging initialized @1857ms WARN [main] c.n.c.s.URLConfigurationSource - No URLs...

bug

When one requests `pierone tags` summary with Pierone CLI like this: ``` pierone tags ci cloud-kraken ``` it sometimes shows outdated information (NO_CVES_FOUND, for example), however, `pierone cves` shows up-to-date...

bug

The exception was thrown during `senza create`: Generating Cloud Formation template.. EXCEPTION OCCURRED: HTTPSConnectionPool(host='pierone.stups.zalan.do', port=443): Read timed out. (read timeout=10) Unknown Error: HTTPSConnectionPool(host='pierone.stups.zalan.do', port=443): Read timed out. (read timeout=10). Please...

It would be nice to know if some of the reported vulnerabilities were introduced in the topmost docker build or were inherited from the base image. For example, this image...

The stupid Docker client will not honor any standard HTTP status code (e.g. 401/403 will just result in "< nil >" printed by the Docker client) --- we need to...