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

Support config and limit #5

Open
wzshiming opened this issue Jun 9, 2024 · 31 comments
Open

Support config and limit #5

wzshiming opened this issue Jun 9, 2024 · 31 comments

Comments

@wzshiming
Copy link
Member 

storage:
  driver: oss
  parameters: {}
  redirectLinks: ""
  linkExpires: 1h

mirrors:
- domain: "registry-1.docker.io"
  alias:
  - "docker.io"
  auth:
    username: xxx
    password: xxx

  limitRules:
  - matchImage: *
    request: 100r/m
    bandwidth: 10G/h
  - matchIP: 0.0.0.0/0
    bandwidth: 100m/m

limitRules:
- matchIP: 0.0.0.0/0
  bandwidth: 500m/m
@gebangfeng
Copy link
Contributor

这个是配置文件吗，我应该如何使用呢

@wzshiming
Copy link
Member Author

计划支持的限流的能力, 在纠结是否有这么细粒度的必要

@gebangfeng
Copy link
Contributor

代理服务器拉取镜像过多会触发这个：
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
匿名用户6个小时有100个镜像拉取额度，登录后可以增加到200个，但貌似没法登录。

@wzshiming
Copy link
Member Author

是的 你需要给 crproxy 配置一个 docker 账号

@wzshiming
Copy link
Member Author

参考 -u 参数 user:[email protected]

@gebangfeng
Copy link
Contributor

gebangfeng commented Jun 11, 2024 via email

@gebangfeng
Copy link
Contributor

gebangfeng commented Jun 11, 2024 via email

@gebangfeng
Copy link
Contributor

gebangfeng commented Jun 11, 2024 via email

@wzshiming
Copy link
Member Author

如果你要本地存储, 建议用 https://github.com/distribution/distribution

@wzshiming
Copy link
Member Author

这个项目最初就是配合 https://github.com/distribution/distribution 一起, 作为一个多源聚代理合用的

@gebangfeng
Copy link
Contributor

gebangfeng commented Jun 11, 2024 via email

@gebangfeng
Copy link
Contributor 

./crproxy_linux_amd64 -a :8888 --total-blobs-speed-limit "20MB" --blobs-speed-limit "1MB"

这两个限制参数有详细说明吗，假如我服务器带宽30M，这两个参数我应该配置多少。

另外

cat registry/config.yml 
version: 0.1
log:
  accesslog:
    #disabled: true
    disabled: false
storage:
  cache:
    blobdescriptor: inmemory
  filesystem:
    rootdirectory: "/var/lib/registry"
  maintenance:
    uploadpurging:
      enabled: false
    readonly:
      enabled: true
http:
  addr: :5000
  headers:
    X-Content-Type-Options: [nosniff]

health:
  storagedriver:
    enabled: false

validation:
  disabled: true

proxy:
  remoteurl: http://crproxy:8080

如果crproxy在registry后面貌似没法使用 ip的限制了，因为它获取不到客户端真实地址：

./crproxy_linux_amd64 --ips-speed-limit "10"

1 similar comment
@gebangfeng
Copy link
Contributor 

./crproxy_linux_amd64 -a :8888 --total-blobs-speed-limit "20MB" --blobs-speed-limit "1MB"

这两个限制参数有详细说明吗，假如我服务器带宽30M，这两个参数我应该配置多少。

另外

cat registry/config.yml 
version: 0.1
log:
  accesslog:
    #disabled: true
    disabled: false
storage:
  cache:
    blobdescriptor: inmemory
  filesystem:
    rootdirectory: "/var/lib/registry"
  maintenance:
    uploadpurging:
      enabled: false
    readonly:
      enabled: true
http:
  addr: :5000
  headers:
    X-Content-Type-Options: [nosniff]

health:
  storagedriver:
    enabled: false

validation:
  disabled: true

proxy:
  remoteurl: http://crproxy:8080

如果crproxy在registry后面貌似没法使用 ip的限制了，因为它获取不到客户端真实地址：

./crproxy_linux_amd64 --ips-speed-limit "10"

@wzshiming
Copy link
Member Author

是的, 限流不适合在 registry 后面使用.

@wzshiming
Copy link
Member Author

我现在部署的形式在服务器上已经把 registry 这一层拿掉了

@gebangfeng
Copy link
Contributor

这种可以，但不支持本地存储。

@wzshiming
Copy link
Member Author

你是想在 服务器 上本地文件 存 blobs?

@wzshiming
Copy link
Member Author

服务器磁盘够??

@gebangfeng
Copy link
Contributor

如果registry 中已经有的镜像，就不会找crproxy了吧

@gebangfeng
Copy link
Contributor

腾讯oss可以挂载磁盘上

@wzshiming
Copy link
Member Author

那服务器带宽呢?

@wzshiming
Copy link
Member Author

这种场景, 我建议你在前面的 nginx 配置限流

@wzshiming
Copy link
Member Author

crproxy 不做任何限制

@gebangfeng
Copy link
Contributor

oss和服务器之间走内网，上下都免费。只收存储费用。

@wzshiming
Copy link
Member Author

oss和服务器之间走内网，上下都免费。只收存储费用。

这个我知道, 我是只服务的外网下行带宽, 这部分一般超过 5M 就很贵

@wzshiming
Copy link
Member Author

wzshiming commented Jun 13, 2024 •
edited
Loading

5M基本上, 拉一两个大镜像就能导致你服务器带宽占满

@gebangfeng
Copy link
Contributor

请问：
我现在的架构是 nginx->官方registry(数据保存磁盘)-->crproxy,
磁盘中的数据量越来越大了，如何分析 拉取量低的，并将它们删除呢。

@wzshiming
Copy link
Member Author

写个脚本分析 nginx 日志统计使用量然后删除, 或者等 7 天会自己 GC

@gebangfeng
Copy link
Contributor

gebangfeng commented Jun 17, 2024 via email

@wzshiming
Copy link
Member Author

是的 七天 不用就删除

@wzshiming
Copy link
Member Author

这种机制, 适合在内网集群做缓存, 不太适合提供公开服务

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wzshiming @gebangfeng