
!GitHub Workflow Status !GitHub stars !Docker Stars !Docker Pulls
!https://raw.githubusercontent.com/atmoz/sftp/master/openssh.png "Powered by OpenSSH"
Dockerfile linksEasy to use SFTP (SSH File Transfer Protocol) server with OpenSSH.
SFTP_USERS environment variable
or (3) in file mounted as /etc/sftp/users.conf (syntax:
user:pass[:e][:uid[:gid[:dir1[,dir2]...]]] ..., see below for examples)
/etc/ssh/ssh_host_*)docker run -p 22:22 -d atmoz/sftp foo:pass:::upload
User "foo" with password "pass" can login with sftp and upload files to a folder called "upload". No mounted directories or custom UID/GID. Later you can inspect the files and use --volumes-from to mount them somewhere else (or see next example).
Let's mount a directory and set UID:
docker run \ -v <host-dir>/upload:/home/foo/upload \ -p 2222:22 -d atmoz/sftp \ foo:pass:1001
sftp: image: atmoz/sftp volumes: - <host-dir>/upload:/home/foo/upload ports: - "2222:22" command: foo:pass:1001
The OpenSSH server runs by default on port 22, and in this example, we are forwarding the container's port 22 to the host's port 2222. To log in with the OpenSSH client, run: sftp -P 2222 foo@<host-ip>
docker run \ -v <host-dir>/users.conf:/etc/sftp/users.conf:ro \ -v mySftpVolume:/home \ -p 2222:22 -d atmoz/sftp
foo:123:1001:100 bar:abc:1002:100 baz:xyz:1003:100
Add :e behind password to mark it as encrypted. Use single quotes if using terminal.
docker run \ -v <host-dir>/share:/home/foo/share \ -p 2222:22 -d atmoz/sftp \ 'foo:$1$0G2g0GSt$ewU0t6GXG15.0hWoOX8X9.:e:1001'
Tip: you can use https://hub.docker.com/r/atmoz/makepasswd/ to generate encrypted passwords:
echo -n "your-password" | docker run -i --rm atmoz/makepasswd --crypt-md5 --clearfrom=-
Mount public keys in the user's .ssh/keys/ directory. All keys are automatically appended to .ssh/authorized_keys (you can't mount this file directly, because OpenSSH requires limited file permissions). In this example, we do not provide any password, so the user foo can only login with his SSH key.
docker run \ -v <host-dir>/id_rsa.pub:/home/foo/.ssh/keys/id_rsa.pub:ro \ -v <host-dir>/id_other.pub:/home/foo/.ssh/keys/id_other.pub:ro \ -v <host-dir>/share:/home/foo/share \ -p 2222:22 -d atmoz/sftp \ foo::1001
This container will generate new SSH host keys at first run. To avoid that your users get a MITM warning when you recreate your container (and the host keys changes), you can mount your own host keys.
docker run \ -v <host-dir>/ssh_host_ed25519_key:/etc/ssh/ssh_host_ed25519_key \ -v <host-dir>/ssh_host_rsa_key:/etc/ssh/ssh_host_rsa_key \ -v <host-dir>/share:/home/foo/share \ -p 2222:22 -d atmoz/sftp \ foo::1001
Tip: you can generate your keys with these commands:
ssh-keygen -t ed25519 -f ssh_host_ed25519_key < /dev/null ssh-keygen -t rsa -b 4096 -f ssh_host_rsa_key < /dev/null
Put your programs in /etc/sftp.d/ and it will automatically run when the container starts.
See next section for an example.
If you are using --volumes-from or just want to make a custom directory available in user's home directory, you can add a script to /etc/sftp.d/ that bindmounts after container starts.
#!/bin/bash # File mounted as: /etc/sftp.d/bindmount.sh # Just an example (make your own) function bindmount() { if [ -d "$1" ]; then mkdir -p "$2" fi mount --bind $3 "$1" "$2" } # Remember permissions, you may have to fix them: # chown -R :users /data/common bindmount /data/admin-tools /home/admin/tools bindmount /data/common /home/dave/common bindmount /data/common /home/peter/common bindmount /data/docs /home/peter/docs --read-only
NOTE: Using mount requires that your container runs with the CAP_SYS_ADMIN capability turned on. https://github.com/atmoz/sftp/issues/60#issuecomment-332909232.
The biggest differences are in size and OpenSSH version. https://hub.docker.com/_/alpine/ is 10 times smaller than https://hub.docker.com/_/debian/. OpenSSH version can also differ, as it's two different teams maintaining the packages. Debian is generally ***ed more stable and only bugfixes and security fixes are added after each Debian release (about 2 years). Alpine has a faster release cycle (about 6 months) and therefore newer versions of OpenSSH. As I'm writing this, Debian has version 7.4 while Alpine has version 7.5. Recommended reading: Comparing Debian vs Alpine for container & Docker apps
It depends on which linux distro and version you choose (see available images at the top). You can see what version you get by checking the distro's packages online. I have provided direct links below for easy access.
openssh packages on Alpine releasesopenssh-server packages on Debian releasesNote: The time when this image was last built can delay the availability of an OpenSSH release. Since this is an automated build linked with https://hub.docker.com/_/debian/ and https://hub.docker.com/_/alpine/ repos, the build will depend on how often they push changes (out of my control). Typically this can take 1-5 days, but it can also take longer. You can of course make this more predictable by cloning this repo and run your own build manually.



探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务