Dockerhub/ Public Docker Images prebuilt, please?

[BloodyIron]

🔖 Feature description

Can we please have this project expanded to offer prebuilt docker images, perhaps hosted on dockerhub or some sort of other public image registry? I for one really would appreciate that if it can be done. :)

🎤 Why is this feature needed ?

This can help streamline adoption of the tool for environments that use docker, kubernetes, or other ecosystems that use docker images. It removes the current requirement of building the image yourself and storing it yourself, which isn't an option in all environments of this nature.

✌️ How do you aim to achieve this?

By asking VERY nicely.

🔄️ Additional Information

No response

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

[ThreeCO]

Is it not enough to use the docker-compose information / image from this description?

https://docs.postiz.com/installation/docker-compose

[BloodyIron]

Honestly no, I mentioned that requires building the image and storing it myself. Most of us really don't have an image repo self-hosted, and it's very commonplace for docker hub or other spaces to host public images for projects just like this one. Stuffing a docker compose into a kubernetes cluster is not exactly a small ask, but pulling an existing public docker image is generally the way to go.

[nevo-david]

Can you please elaborate on the limitation you have for a built docker?
We can have more environments if there is something specific.

[BloodyIron]

Can you please elaborate on the limitation you have for a built docker? We can have more environments if there is something specific.

From a workflow perspective, assuming maybe you're not quite seeing how I use docker images publicly hosted...

When I say "this thing" or whatnot in the description below, it's anything, not just "postiz-app", like it could be Bookstack, nextCloud, a game server, many things.

I define YAML code for the various kubernetes objects related to something I want to "spin-up". I'll declare the NGINX Ingress stuff (what port(s) I'll use, if I want any custom configurations for this particular thing), the storage aspects (Persistent Volume/Persistent Volume Claim, PV/PVC) "this thing", and then also the deployment/daemonset/whatever that then defines how the container(s) run (sometimes I also need supporting containers running like say mysql). When I define how the container(s) run I'll declare which docker image I pull, the source, and the tag (latest, or a specific version, or whatever). In many cases that source is docker hub, but there's other public image repos too.

I define all this YAML manifest content in my IDE of preference (in my case VSCodium), and commit it to my git repo (GitLab in this case). And I have different repos for different kubernetes clusters, and/or namespaces.

I then have this component ArgoCD which checks all relevant repos every 10 seconds for any content changes. When it detects the change I committed, it evaluates the change against the running-config state of the relevant kubernetes cluster. If I didn't fat-finger anything (syntax issue, etc) then it will try to apply the changes to that cluster automatically. Assuming I did it right, this will mean the new container(s) spin-up in the cluster, and the cluster itself decides which kubernetes node the new toy runs on.

None of that includes docker compose, and pulls from public image repos using pre-built docker images.

Does that clarify?

[jamesread]

Hey @BloodyIron, sorry, I've been away from contributions on this project for December because I've been super busy with work. I've been maintaining the linux container images.

Postiz already has container images published to the GitHub Container Registry (GHCR); https://github.com/orgs/gitroomhq/packages?repo_name=postiz-app

Docker Hub is incredibly problematic, it rate limits, and it charges users that use a lot of bandwith (and the Postiz containers are pretty large), that is why we publish to GHCR instead.

Documentation on how to use the Postiz containers can be found here; https://docs.postiz.com/installation/docker-compose