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

Support for arm #102

Open
mineichen opened this issue Dec 11, 2017 · 10 comments · May be fixed by #245
Open

Support for arm #102

mineichen opened this issue Dec 11, 2017 · 10 comments · May be fixed by #245

Comments

@mineichen
Copy link

mineichen commented Dec 11, 2017

I'm currently using your sftp-Project on a ARM-Device. To do so, I forked your Github-Repository and created a new branch called "armhf-alpine", which is based on the "alpine" branch. I actually wanted to make a pull-Request, but I think it's not possible if I want to merge into a new branch.

Please create a new branch based on the "alpine" branch if you are interested to include it in your repository. It would be nice if you can update the Docker-Hub-Readme to provide instructions on how to build it.

Maybe you can even build a docker-image or upload the one provided by me "mineichen/sftp:armhf-alpine-3.6" for convenience, because ARM is not supported for automated builds as far as i know.

Thank you for all your work!

Regards, Markus

@atmoz
Copy link
Owner

atmoz commented Dec 11, 2017

I want to limit the number of branches that I have to maintain. If hub.docker.com does not support automated builds for ARM and there is just one line difference from the alpine branch, I think it's better to add some instructions in the README.md and maybe make a simple script that does what is necessary to start the build (e.g. making a copy of the Dockerfile with modification and preparing for build on ARM).

I don't have time to test any ARM setup before January

@atmoz
Copy link
Owner

atmoz commented Mar 12, 2018

Still busy at the moment.

If someone has the time, suggestions for build instructions/script (or something else) would be appreciated.

@Hayo-Baan
Copy link

Is there any progress made on this issue? I'm running an M1 Mac and would very much like to be able to run a arm64 version of the sftp server.

@b2un0
Copy link

b2un0 commented Mar 22, 2022

@atmoz you should switch to the official qemu dockerx build actions

https://github.com/b2un0/docker-netcup-dyndns/blob/master/.github/workflows/container.yml

@harald-walker-sympower
Copy link

@HayoBaanAtHand the image from @kalioz works on M1 Macs.

@Hayo-Baan
Copy link

Thanks @harald-walker-sympower, I will investigate this!

@roball24
Copy link

roball24 commented Jan 4, 2023

On Apple silicon Macs at least you can still run this in a docker container opened through a rosetta terminal.

Duplicate your preferred terminal application.
Set the duplicate to open with rosetta (instructions here: https://support.apple.com/en-us/HT211861 )

Then you'll be able to run this container inside any shell of your new rosetta terminal application.

You can even run this docker container in a rosetta/intel shell while other containers remain running in a default arm64 shell. Cheers!

@Hayo-Baan
Copy link

Hi @roball24, starting it from a Rosetta terminal instantiation is not even necessary; starting it from a normal Terminal also works just fine. And so does auto starting it when docker desktop starts (I created the container with --restart always)

@jmcombs
Copy link
Contributor

jmcombs commented Mar 15, 2023

I forked this repository a few months ago to fix the (now fixed) automated build issue, as well as add SCP support and to build multi-platform images (including ARM). So, you can run it on the Raspberry Pi or Apple Silicon based machines. Docker Image - jmcombs/sftp & just in case you want to review the code: jmcombs/sftp

@b2un0
Copy link

b2un0 commented Mar 16, 2023

finally i switch to https://github.com/drakkan/sftpgo

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

Successfully merging a pull request may close this issue.

7 participants