Seamark Registry
@seamark.cr
Seamark (formally ATCR) - Distributed Container Registry Developer - @evan.jarrett.net
Like everyone else, I am looking into how to add Spaces to at-container-registry and @seamark.cr The original permission structure maps cleanly to Spaces. One thing spaces can allow for is more granular permissions for users on who can download their containers. ie "private container images"
We have passed 500 registered users! Some other stats: over 50 users using the credential helper to push/pull images. over 100 users have signed into the site in the last 30 days. 6 users are hosting their own storage.
I haven't posted in awhile but I can assure you the project is not dead. Some of you may have noticed the rebrand. The primary reason is to have a hosted solution that is separate from the open source project. There will likely be a long-form explaining all this in the future.
Finally solved both the oauth scopes and login naming debate with the new Login page:
Certified architecturally correct
Central@central.comind.network · 5mo agoContainer registry on ATProto. Your handle is your registry namespace, manifests live in your PDS, blobs in hold services. The manifest/blob split is architecturally correct - PDS for small signed records, external storage for the actual layers.
Two new features being worked on: - New layer commands and vulnerabilities page. - The ability to change your preferred client from docker. This changes all the pull commands on the site.
The other batch of stickers arrived. These are much more vibrant compared to the first batch and do not have the white border. Really happy how these turned out. There is ~100 of each style for #atmosphereconf
First batch of stickers for #atmosphereconf arrived. Getting them from 2 different suppliers with slightly different styles so there will be plenty to hand out.
Big changes happening. Vulnerability scanning has (mostly) landed. you can take a look at the example here atcr.io/r/evan.jarre... It will be processing images in the background and eventually on push. This is built using Syft and Grype. and records are stored in the holds embedded pds
Haven't posted in awhile but that doesn't mean big things aren't being done. Lots of changes coming soon!
Spent the weekend micro-optimizing everything on the atcr.io page rendering and navigation should be much faster, and avatars are now not trying to load the full native resolution.
Spent some time on the UI. The homepage got more of a redesign. Also added the ability for data export and deletions, so data that is stored by ATCR, but not in your PDS can be viewed/removed at any time.
In addition to working on quotas, An admin dashboard was added to Holds to manage access, quotas, view metrics etc. This is all running off public data from PDS, but gives an easy way to view/edit.
Been working on adding quotas to the Holds (storage sidecars) These are optional and fully configurable with different tiers that can be added to crew records. It is set to 5GB currently for the provided storage on @hold01.atcr.io The largest account so far is 3.3GB
Also new in atcr.io if you add a source label to your build: --label org.opencontainers.image.source="github or gitlab or tangled url" The README will be fetched and displayed as the description.
New in atcr.io you can edit your repo's avatar from the UI. This requires updated oauth scopes, so you will need to log out and back in. Note this also applies using labels/annotations when building: --label io.atcr.io="https://my.cool/image.png"
@atcr.io just pushed hold:latest Digest: sha256:1ddc828a25... Size: 12.1 MB
@atcr.io just pushed appview:latest Digest: sha256:8a9052ba4d... Size: 15.0 MB
