Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cleaned up registry and improved logging #378

Merged
merged 3 commits into from
Jan 9, 2025
Merged

cleaned up registry and improved logging #378

merged 3 commits into from
Jan 9, 2025

Conversation

zackbradys
Copy link
Member

@zackbradys zackbradys commented Dec 12, 2024 •
edited
Loading

Please check below, if the PR fulfills these requirements:

  • Commit(s) and code follow the repositories guidelines.
  • Test(s) have been added or updated to support these change(s).
  • Doc(s) have been added or updated to support these change(s).

Associated Links:

  • N/A

Types of Changes:

  • Feature

Proposed Changes:

  • TBD

Verification/Testing of Changes:

zackbradys@Zacks-MacBook-Pro hauler % ./dist/hauler_darwin_arm64_v8.0/hauler store info                                        
+-----------------------+-------+----------+----------+----------+
| REFERENCE             | TYPE  | PLATFORM | # LAYERS | SIZE     |
+-----------------------+-------+----------+----------+----------+
| hauler/core:2.8.3     | chart | -        |        1 | 33.3 kB  |
| hauler/gitea:10.6.0   | chart | -        |        1 | 396.3 kB |
| hauler/rancher:2.10.0 | chart | -        |        1 | 15.1 kB  |
| hauler/vault:0.29.1   | chart | -        |        1 | 49.6 kB  |
+-----------------------+-------+----------+----------+----------+
|                                             TOTAL   | 494.3 KB |
zackbradys@Zacks-MacBook-Pro hauler % 
zackbradys@Zacks-MacBook-Pro hauler % 
zackbradys@Zacks-MacBook-Pro hauler % ./dist/hauler_darwin_arm64_v8.0/hauler store serve registry --port 5001
2024-12-14 09:21:33 INF hauler/rancher:2.10.0
2024-12-14 09:21:33 INF 2024/12/14 09:21:33 existing manifest: 2.10.0@sha256:1e42b0e226e80a21ebc13b6a1d5618d75026f3b2bb23ffc0dba5f3b40f78e716
2024-12-14 09:21:33 INF hauler/core:2.8.3
2024-12-14 09:21:33 INF 2024/12/14 09:21:33 existing manifest: 2.8.3@sha256:c9e02c5a9c35d6517b6aaab6dfa7dbf2e4a6447098fa8a30a081bc239bc50d79
2024-12-14 09:21:33 INF hauler/vault:0.29.1
2024-12-14 09:21:33 INF 2024/12/14 09:21:33 existing manifest: 0.29.1@sha256:b6b0c74906cc3b4c2e2393d6dcdc9ddedbcf9aeafa6927d762d8ddd946b19f51
2024-12-14 09:21:33 INF hauler/gitea:10.6.0
2024-12-14 09:21:33 INF 2024/12/14 09:21:33 existing manifest: 10.6.0@sha256:bf9a9fc761582f9f8c1a7b8f6f3c04a0b3a8d2392e184302ccbfa6e29819441b
2024-12-14 09:21:33 INF copied artifacts to [127.0.0.1:62719]
2024-12-14 09:21:33 INF starting registry on port [5001]
2024-12-14 09:21:33 INF using registry configuration... 
version: "0.1"
log:
    level: info
storage:
    cache:
        blobdescriptor: inmemory
    filesystem:
        rootdirectory: registry
    maintenance:
        readonly:
            enabled: true
http:
    addr: :5001
    headers:
        X-Content-Type-Options:
            - nosniff
validation:
    manifests:
        urls:
            allow:
                - .+
WARN[0001] No HTTP secret provided - generated random secret. This may cause problems with uploads if multiple registries are behind a load-balancer. To provide a shared secret, fill in http.secret in the configuration file or set the REGISTRY_HTTP_SECRET environment variable.  go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] Starting upload purge in 25m0s                go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] redis not configured                          go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] using inmemory blob descriptor cache          go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] listening on [::]:5001                        go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
zackbradys@Zacks-MacBook-Pro hauler % ./dist/hauler_darwin_arm64_v8.0/hauler store info --log-level debug
2024-12-14 09:21:05 DBG running cli command [hauler store info]
2024-12-14 09:21:05 DBG using hauler directory at [/Users/zackbradys/.hauler]
2024-12-14 09:21:05 DBG using store at [/Users/zackbradys/Documents/Coding/GitHub/hauler/store]
+-----------------------+-------+----------+----------+----------+
| REFERENCE             | TYPE  | PLATFORM | # LAYERS | SIZE     |
+-----------------------+-------+----------+----------+----------+
| hauler/core:2.8.3     | chart | -        |        1 | 33.3 kB  |
| hauler/gitea:10.6.0   | chart | -        |        1 | 396.3 kB |
| hauler/rancher:2.10.0 | chart | -        |        1 | 15.1 kB  |
| hauler/vault:0.29.1   | chart | -        |        1 | 49.6 kB  |
+-----------------------+-------+----------+----------+----------+
|                                             TOTAL   | 494.3 KB |
+-----------------------+-------+----------+----------+----------+
zackbradys@Zacks-MacBook-Pro hauler % 
zackbradys@Zacks-MacBook-Pro hauler % 
zackbradys@Zacks-MacBook-Pro hauler % ./dist/hauler_darwin_arm64_v8.0/hauler store serve registry --port 5001 --log-level debug
2024-12-14 09:22:10 DBG running cli command [hauler store serve registry]
2024-12-14 09:22:10 DBG using hauler directory at [/Users/zackbradys/.hauler]
2024-12-14 09:22:10 DBG using store at [/Users/zackbradys/Documents/Coding/GitHub/hauler/store]
2024-12-14 09:22:10 DBG identified registry target reference of [127.0.0.1:62983]
2024-12-14 09:22:11 INF hauler/rancher:2.10.0
2024-12-14 09:22:11 INF 2024/12/14 09:22:11 existing manifest: 2.10.0@sha256:1e42b0e226e80a21ebc13b6a1d5618d75026f3b2bb23ffc0dba5f3b40f78e716
2024-12-14 09:22:11 INF hauler/core:2.8.3
2024-12-14 09:22:11 INF 2024/12/14 09:22:11 existing manifest: 2.8.3@sha256:c9e02c5a9c35d6517b6aaab6dfa7dbf2e4a6447098fa8a30a081bc239bc50d79
2024-12-14 09:22:11 INF hauler/vault:0.29.1
2024-12-14 09:22:11 INF 2024/12/14 09:22:11 existing manifest: 0.29.1@sha256:b6b0c74906cc3b4c2e2393d6dcdc9ddedbcf9aeafa6927d762d8ddd946b19f51
2024-12-14 09:22:11 INF hauler/gitea:10.6.0
2024-12-14 09:22:11 INF 2024/12/14 09:22:11 existing manifest: 10.6.0@sha256:bf9a9fc761582f9f8c1a7b8f6f3c04a0b3a8d2392e184302ccbfa6e29819441b
2024-12-14 09:22:11 INF copied artifacts to [127.0.0.1:62983]
2024-12-14 09:22:11 INF starting registry on port [5001]
2024-12-14 09:22:11 INF using registry configuration... 
version: "0.1"
log:
    level: debug
storage:
    cache:
        blobdescriptor: inmemory
    filesystem:
        rootdirectory: registry
    maintenance:
        readonly:
            enabled: true
http:
    addr: :5001
    headers:
        X-Content-Type-Options:
            - nosniff
validation:
    manifests:
        urls:
            allow:
                - .+
2024-12-14 09:22:11 DBG detailed registry configuration: &{Version:0.1 Log:{AccessLog:{Disabled:false} Level:debug Formatter: Fields:map[] Hooks:[]} Loglevel: Storage:map[cache:map[blobdescriptor:inmemory] filesystem:map[rootdirectory:registry] maintenance:map[readonly:map[enabled:true]]] Auth:map[] Middleware:map[] Reporting:{Bugsnag:{APIKey: ReleaseStage: Endpoint:} NewRelic:{LicenseKey: Name: Verbose:false}} HTTP:{Addr::5001 Net: Host: Prefix: Secret: RelativeURLs:false DrainTimeout:0s TLS:{Certificate: Key: ClientCAs:[] MinimumTLS: CipherSuites:[] LetsEncrypt:{CacheFile: Email: Hosts:[]}} Headers:map[X-Content-Type-Options:[nosniff]] Debug:{Addr: Prometheus:{Enabled:false Path:}} HTTP2:{Disabled:false}} Notifications:{EventConfig:{IncludeReferences:false} Endpoints:[]} Redis:{Addr: Password: DB:0 TLS:{Enabled:false} DialTimeout:0s ReadTimeout:0s WriteTimeout:0s Pool:{MaxIdle:0 MaxActive:0 IdleTimeout:0s}} Health:{FileCheckers:[] HTTPCheckers:[] TCPCheckers:[] StorageDriver:{Enabled:false Interval:0s Threshold:0}} Proxy:{RemoteURL: Username: Password:} Compatibility:{Schema1:{TrustKey: Enabled:false}} Validation:{Enabled:false Disabled:false Manifests:{URLs:{Allow:[.+] Deny:[]}}} Policy:{Repository:{Classes:[]}}}
DEBU[0001] using "text" logging formatter               
WARN[0001] No HTTP secret provided - generated random secret. This may cause problems with uploads if multiple registries are behind a load-balancer. To provide a shared secret, fill in http.secret in the configuration file or set the REGISTRY_HTTP_SECRET environment variable.  go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] redis not configured                          go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] Starting upload purge in 48m0s                go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] using inmemory blob descriptor cache          go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown
INFO[0001] listening on [::]:5001                        go.version="go1.23.4 X:boringcrypto" version=v3.0.0+unknown

Additional Context:

  • N/A

@zackbradys zackbradys self-assigned this Dec 12, 2024
@zackbradys zackbradys added enhancement New feature or request size/S Denotes an issue/PR requiring a relatively small amount of work labels Dec 12, 2024
@zackbradys zackbradys added this to the Hauler v1.2.0 milestone Dec 12, 2024
@zackbradys zackbradys requested a review from a team December 14, 2024 14:55
@zackbradys zackbradys requested review from a team and removed request for a team January 7, 2025 17:48
@CamrynCarter CamrynCarter mentioned this pull request Jan 7, 2025
Closed
amartin120
amartin120 approved these changes Jan 9, 2025
View reviewed changes
Copy link
Contributor

@amartin120 amartin120 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @zackbradys

@zackbradys zackbradys merged commit e97adcd into hauler-dev:main Jan 9, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@amartin120 amartin120 amartin120 approved these changes

Assignees

@zackbradys zackbradys

Labels
enhancement New feature or request size/S Denotes an issue/PR requiring a relatively small amount of work
Projects
Hauler
Status: Resolved
Milestone
Hauler v1.1-next1
Development

Successfully merging this pull request may close these issues.
3 participants
@zackbradys @amartin120 @CamrynCarter