Publish an official Docker Image in ghcr.

[luisalrp]

Would be really useful to have an official Docker Image to pull.

Describe the solution you'd like

A Github Action that creates the Docker Image with each release, tag it properly and upload it to ghcr or dockerhub.

Describe alternatives you've considered

An alternative is really ugly. It is being aware of each release and do it manually or use some cicd to do it.

Thanks!

[v1xingyue]

#889

[luisalrp]

Hey @v1xingyue,

Thanks for the PR. I noticed there was a release, but I can't see the package, while if I go to the Create and publish a Docker image action, I can see they were ok. Not sure whats happening. Maybe its a rights problem?

Thanks!

[v1xingyue]

Ya @luisalrp I checked the log action running. It tells image has been pushed:

But When I pull one image from my cloud server.
It tells no unauthorized :

I'm not sure, is it the problem of permission?

[v1xingyue]

Also github shows we have one public image. But we can't see. Maybe we should check the settings about package.

This is one of my image settings,maybe our package is private.

Or maybe we should change our org package settings:

https://github.com/organizations/ai16z/settings/packages

[luisalrp]

Yeah, I think its something about visibility (sorry for using rights instead of visibility). When I tried to pull it, I got the same unauthorized as you. Not sure how to solve it.

I went to Solve Problems in Work with containers registry, and there is nothing about it.

I asked xAi and it says that packages by default sets to private.

I hope it helps. Thanks!

[v1xingyue]

I think we may change this package to public ? @lalalune

[luisalrp]

Hey, @v1xingyue, @lalalune;

I created a PR to change package visibility when creating new releases, so no need to manually change visibility on future releases. I'm happy to have contributed a little bit.

Best, Luis.

[v1xingyue]

Wow thanks that's so cool, Wait for next release.

[v1xingyue]

Hey, @v1xingyue, @lalalune;

I created a PR to change package visibility when creating new releases, so no need to manually change visibility on future releases. I'm happy to have contributed a little bit.

Best, Luis.

Hey, your pr about change visibility runs failed , it returns 404

https://github.com/elizaOS/eliza/actions/runs/12452080982/job/34760652944#step:7:1

[luisalrp]

Sorry for that. Then it can be done only by config. Configuring a package's access control and visibility.

I created a PR to delete the non working task.

[v1xingyue]

Ya that's really true. So let's change the package visibility @lalalune

[luisalrp]

Hey frens!

Any ETA for this? It is a pity that being done, it can't be used due to package visibility config. @v1xingyue, do you know if there is someone else with the rights to change package visibility? I understand that with Christmas and road show in Asia it is being busy days for @lalalune 😊

Best, Luis!

[luisalrp]

Maybe @shakkernerd can change package visibility? I've seen publishing the releases 😃

[Kevin-Mok]

Also hoping to try using the Docker package soon!

[shakkernerd]

Maybe @shakkernerd can change package visibility? I've seen publishing the releases 😃

I will take a look at this.