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.

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

wrong linux/amd64 docker image #164

Closed
lilunxm12 opened this issue Feb 18, 2025 · 6 comments · Fixed by #165
Closed

wrong linux/amd64 docker image #164

lilunxm12 opened this issue Feb 18, 2025 · 6 comments · Fixed by #165

Comments

@lilunxm12
Copy link

0.1.4-proxy: Pulling from codelion/optillm no matching manifest for linux/amd64 in the manifest list entries

I encountered this error when pulling and it turns out there's no linux/amd64 but only unknown/unknown in the registry

Image

I've checked https://github.com/codelion/optillm/blob/main/.github/workflows/publish.yml but couldn't find what's wrong

@codelion
Copy link
Owner

codelion commented Feb 18, 2025

It looks like the GH Action runner is getting out of space - https://github.com/codelion/optillm/actions/runs/13032992652

Image

Are you able to build the container locally?

@lilunxm12
Copy link
Author

It looks like the GH Action runner is getting out of space - https://github.com/codelion/optillm/actions/runs/13032992652

Image Are you able to build the container locally?

just finished building without error.

Image

And it's really huge for proxy. I see torch and cudnn as pypi dependency, do we really need that for proxy only image?

@codelion
Copy link
Owner

We don't need those for proxy, I suspect it is sneaking in transitively via some other dependency here - https://github.com/codelion/optillm/blob/main/requirements_proxy_only.txt I will review and fix it in next release.

@lilunxm12
Copy link
Author

We don't need those for proxy, I suspect it is sneaking in transitively via some other dependency here - https://github.com/codelion/optillm/blob/main/requirements_proxy_only.txt I will review and fix it in next release.

Oh, my bad, I did not use Dockerfile.proxy_only, I'll try it again now

@lilunxm12
Copy link
Author

Image

That's the result, I think it's still a bit too large for a proxy

@codelion
Copy link
Owner

Image

Managed to reduce the size to 487.25, none of the plugins or local inference would work in the proxy but the main approaches would all work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants