zoukankan      html  css  js  c++  java
  • docker sftp

    直接参考:https://hub.docker.com/r/atmoz/sftp

    Usage

    • Define users in (1) command arguments, (2) 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)
      • Set UID/GID manually for your users if you want them to make changes to your mounted volumes with permissions matching your host filesystem.
      • Directory names at the end will be created under user's home directory with write permission, if they aren't already present.
    • Mount volumes
      • The users are chrooted to their home directory, so you can mount the volumes in separate directories inside the user's home directory (/home/user/mounted-directory) or just mount the whole /home directory. Just remember that the users can't create new files directly under their own home directory, so make sure there are at least one subdirectory if you want them to upload files.
      • For consistent server fingerprint, mount your own host keys (i.e. /etc/ssh/ssh_host_*)

    Examples

    Simplest docker run example

    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).

    Sharing a directory from your computer

    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

    Using Docker Compose:

    sftp:
        image: atmoz/sftp
        volumes:
            - <host-dir>/upload:/home/foo/upload
        ports:
            - "2222:22"
        command: foo:pass:1001

    Logging in

    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>

    Store users in config

    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

    Encrypted password

    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 atmoz/makepasswd to generate encrypted passwords:
    echo -n "your-password" | docker run -i --rm atmoz/makepasswd --crypt-md5 --clearfrom=-

    Logging in with SSH keys

    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

    Providing your own SSH host key (recommended)

    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

    Execute custom scripts or applications

    Put your programs in /etc/sftp.d/ and it will automatically run when the container starts. See next section for an example.

    Bindmount dirs from another location

    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. See this answer for more information.

  • 相关阅读:
    微信h5下拉隐藏网页,还有取消页面滑动
    vuejs中使用递归嵌套组件
    运行gitbook init命令报错及问题解决办法
    利用python生成gitbook目录文件
    通过Appium日志,分析其运行原理
    字符串两两更换位置
    Dockerfile启动的程序,内存不断增长问题
    测试流程优化
    APP测试面试题(一)
    关于面试总结13-app测试面试题
  • 原文地址:https://www.cnblogs.com/lshan/p/15167908.html
Copyright © 2011-2022 走看看