Suggestion: Provide an ARM Build for Docker Image #9

Open
opened 2024-04-20 23:04:11 +00:00 by Korbs · 3 comments

Any chance, in the future, you can provide an arm build of the 4get Docker image?
Currently, I've setup quay.io/sudovanilla/4get for now.

This would allow 4get to run on Docker on other devices such as the Raspberry/Orange/Banana Pi, Pine64, Apple Silicon(for Asahi Linux and such), and more. Although is quite is easy to git clone this repo and run the Docker build command on an arm server, which is what I did.

Side note, could you also push the image to other hubs like Quay and your own Gitea instance? I know Gitea/Forgejo supports pushing Docker images to your own instance, which is pretty cool.

Any chance, in the future, you can provide an arm build of the 4get Docker image? Currently, I've setup [quay.io/sudovanilla/4get](https://quay.io/repository/sudovanilla/4get) for now. This would allow 4get to run on Docker on other devices such as the Raspberry/Orange/Banana Pi, Pine64, Apple Silicon(for Asahi Linux and such), and more. Although is quite is easy to git clone this repo and run the Docker build command on an arm server, which is what I did. Side note, could you also push the image to other hubs like Quay and your own Gitea instance? I know Gitea/Forgejo supports pushing Docker images to your own instance, which is pretty cool.
Owner

I didn't know about selfhosted docker images, I thought it had to be from dockerhub. I can take a look at it. :)

For the ARM image, I can't say I'm really knowledgeable about docker so I will mention my friend so that he may take a look at it... @throwaway

Take care korbs

I didn't know about selfhosted docker images, I thought it had to be from dockerhub. I can take a look at it. :) For the ARM image, I can't say I'm really knowledgeable about docker so I will mention my friend so that he may take a look at it... @throwaway Take care korbs
Author

Alright thanks.
Also building the Docker image for 4get is super easy, very easy since the Dockerfile is already included.

All that needs to be run is:

docker build -t 4get .

You'll need to be specific about the name if you want to push to a different hub, for example if you want to push to Quay then it needs to be:

docker build -t quay.io/USERNAME/4get .
Alright thanks. Also building the Docker image for 4get is super easy, very easy since the `Dockerfile` is already included. All that needs to be run is: ``` docker build -t 4get . ``` You'll need to be specific about the name if you want to push to a different hub, for example if you want to push to Quay then it needs to be: ``` docker build -t quay.io/USERNAME/4get . ```
Contributor

@lolcat Assuming that you're building the image manually from the command line, you just need to have buildx set up and then specify the architecture as an argument, e.g., docker buildx build --platform linux/amd64,linux/arm64 -t luuul/4get:latest -f ./Dockerfile --push .

Ideally, you would have Gitea Actions set up to automatically build and push OCI images to a registry upon a commit or named release, so you wouldn't need to do so manually

@lolcat Assuming that you're building the image manually from the command line, you just need to have [`buildx`](https://github.com/docker/buildx) set up and then specify the architecture as an argument, e.g., `docker buildx build --platform linux/amd64,linux/arm64 -t luuul/4get:latest -f ./Dockerfile --push .` Ideally, you would have [Gitea Actions](https://docs.gitea.com/usage/actions/quickstart) set up to automatically build and push OCI images to a registry upon a commit or named release, so you wouldn't need to do so manually
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lolcat/4get#9
No description provided.