mritd / dockerfile

some personally made dockerfile

Dockerfile

⚠️⚠️⚠️ Note: Some build work of docker image is being migrated to earthly, you may not see the update commit in the current repo.

⚠️⚠️⚠️ Earthfile has better scalability and is more convenient for cross-compilation; the migrated dockerfle can be viewed in https://github.com/mritd/autobuild.

---

This repository contains some dockerfiles of personally created docker images; it will be maintained for long periods if necessary.

The dockerfile for docker images running in a production environment has been moved to ytpay/dockerfiles. such as all in one build image、jdk、tomcat; dockerfiles for these docker images will be maintained for a long time

Stargazers over time

JetBrains

Thanks to JetBrains for providing IDE support for this project, click to buy JetBrains IDE license to support the strongest IDE in the universe.

dockerfile's Issues

无法使用json文件启动ss

您好, 我使用如下命令启动容器, 但没有成功

docker run -d --name ss -p 6443-6446:6443-6446 --mount type=bind,source=/root/shadowsocks.json,target=/etc/shadowsocks.json mritd/shadowsocks -m "ss-server" -s "-c /etc/shadowsocks.json"

请问是我的命令有哪里输入错误了吗?

求更新 https://hub.docker.com/r/mritd/shadowsocks/

shadowsocks-libev 3.0 和 kcptun v20170221
非常感谢！！！

为什么我的ss-server运行一会儿就会失效？

我在一个vm上安装了docker，然后用 mritd/shadowsocks这个image。
启动container后，我的客户端可以正常通过该ss-server:8388访问facebook & google，然后大约几十秒后，就不能正常工作了。
然后我 sudo docker exec -it f99dd2b85054 /bin/bash 到该container里面查看，发现ss-server的进程变成了[ss-server].

正常工作时，显示如下：

bash-4.4# ps aux | grep ss-server
    5 root       0:00 ss-server -s 0.0.0.0 -p 8388 -m aes-256-cfb -k barfoo! --fast-open
   11 root       0:00 grep ss-server

无法工作时，显示如下：

bash-4.4# ps aux | grep ss-server
    5 root       0:00 [ss-server]
   13 root       0:00 grep ss-server

请问一下，这个是怎么回事儿？谢谢！

增加BBR

听说把BBR加上效果更佳，可否添加一下？

请问能通过配置文件配置吗？我想要实现多端口不同密码登陆

如题

How to use "shadowsocks.json" file? if it is ok , could you show the cmd?

关于shadowsocks的docker

有两个问题：

1. kcptun的端口应该设置为udp，即 -p 20000:20000/udp ，默认情况下好像会自动设置成tcp；
2. 开启ota后会出现不能上传的问题，好像是ss自己的锅，并不是很懂。

樱花报错。Jun 29 09:22:13 UTC app name: mritd/shadowsocks process Exited with status 1

cmd 为 /entrypoint.sh -s "-s 0.0.0.0 -p 8388 -m rc4-md5 -k youxiaojie --fast-open" -k "-t 127.0.0.1:8388 -l :29900 -mode fast2" -x

shadowsocks-libev的dockerfile求集成OBFS

https://github.com/shadowsocks/simple-obfs
求集成OBFS, KCPTUN现在已经不好用了,很多IPC限制UDP

shadowsocks 3.1.3 了

出现错误

docker run -it -p 1080:1080 -p server_port:server_port/udp --name ss -e SS_CONFIG="-s 127.0.0.1 -p 1070 -l 1080 -k pwd1 -t 600 -m aes-256-cfb" -e KCP_CONFIG="-t server_ip:server_port -l :1070 -key pwd2 -crypt aes -mode fast2 -mtu 1350 -sndwnd 128 -rcvwnd 1024 -nocomp true" -e KCP_FLAG="true" -d mritd/shadowsocks

ShadowsocksX配置后无法上网

需要如何配置？

shadowsocks UDP port relay not working

Hi,

I used shadowsocks to proxyfy my connections but i cannot manage to forward my UDP ports,
i used this configuration for the server :
docker run -dt --name ssserver -p 6443:6443 -p 6443:6443/udp -p 6500:6500/udp mritd/shadowsocks -m "ss-server" -s "-s 0.0.0.0 -p 6443 -m aes-256-cfb -k mypassword --fast-open -u -d 8.8.8.8" -x -e "kcpserver" -k "-t 127.0.0.1:6443 -l :6500 -mode fast2"

My client is a routeur on openWrt, i can do any TCP connection, but when i try to use UDP it doesnt, (i cannot make my dns go through the relay or make any other udp connection).

Do you know if i configured something wrong ? Thx :)

大佬能不能写一个 Pcap_DNSProxy 的 Dockerfile

项目地址 https://github.com/chengr28/Pcap_DNSProxy
我自己尝试做一个，但是失败了

FROM alpine:3.7

LABEL maintainer="LisonFan <[email protected]>"

ARG TZ='Asia/Shanghai'

ENV TZ $TZ

RUN apk upgrade --update \
    && apk add tzdata \
    && apk add --virtual .build-deps \
        git \
        wget \
        cmake \
        libpcap \
        libpcap-dev \
        libsodium \
        libsodium-dev \
        openssl \
        openssl-dev \
        libevent \
        libevent-dev \
        bash \
        autoconf \
        automake \
        make \
        gcc \
        g++ \
        xmlto \
        build-base \
        c-ares-dev \
        libev-dev \
        libtool \
        linux-headers \
        pcre-dev \
        musl-dev \
    && ( cd root \
    && wget -c -O Pcap_DNSProxy.tar.gz https://github.com/chengr28/Pcap_DNSProxy/archive/v0.4.9.6.tar.gz \
    && tar zxf Pcap_DNSProxy.tar.gz \
    && mv Pcap_DNSProxy-0.4.9.6 Pcap_DNSProxy \
    && rm -rf Pcap_DNSProxy.tar.gz \
    && cd Pcap_DNSProxy/Source/Auxiliary/Scripts \
    && chmod 755 CMake_Build.sh \
    && ./CMake_Build.sh ) \
    && ln -sf /usr/share/zoneinfo/$TZ /etc/localtime \
    && echo $TZ > /etc/timezone \
    && apk del .build-deps

为什么我的ss端口和kcp的端口冲突？有一个服务无法启动。

shadowsocks的配置如下：

{
    "server":"0.0.0.0",
    "server_port":8388,
    "local_port":1080,
    "password":"mypassword",
    "method":"aes-256-cfb",
    "timeout":60
}

启动后运行 netstat -nl 查看端口，

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
tcp        0      0 10.81.180.166:16001     0.0.0.0:*               LISTEN     
tcp6       0      0 :::22                   :::*                    LISTEN     
tcp6       0      0 :::8388                 :::*                    LISTEN     
udp        0      0 0.0.0.0:44851           0.0.0.0:*                          
udp        0      0 0.0.0.0:68              0.0.0.0:*                          
udp6       0      0 :::6120                 :::*                     

可以看到，8388端口已经被占用了（此时用ss客户端直连，是可以工作的）
然后，再启动kcp时就发现失败，kcp无法启动，socks服务无法打开。

kcp server 配置如下：

{
    "listen": ":6500",
    "target": "127.0.0.1:8388",
    "key": "it is secret.",
    "crypt": "aes",
    "mode": "fast2",
    "mtu": 1350,
    "sndwnd": 1024,
    "rcvwnd": 1024,
    "nocomp": false
}

或者，我先启动kcp-server，是可以成功的。然后再启动shadowsocks也会失败，也是8388端口被占用了。

请问大神，这是怎么回事？
thx.

This system doesn't provide enough entropy to quickly generate high-quality random numbers.

Using the latest version on GCP, got the following logs.

2018-07-31 14:18:28:�[33mKcptun not started......�[0m
2018-07-31 14:18:28:�[32mStarting shadowsocks......�[0m
2018-07-31 14:18:28: 2018-07-31 14:18:28 INFO: using tcp fast open
2018-07-31 14:18:28: 2018-07-31 14:18:28 INFO: initializing ciphers... aes-256-cfb
2018-07-31 14:18:28: 2018-07-31 14:18:28 INFO: This system doesn't provide enough entropy to quickly generate high-quality random numbers.
2018-07-31 14:18:28:Installing the rng-utils/rng-tools, jitterentropy or haveged packages may help.
2018-07-31 14:18:28:On virtualized Linux environments, also consider using virtio-rng.
2018-07-31 14:18:28:The service will not start until enough entropy has been collected.
2018-07-31 14:18:28:
2018-07-31 14:18:28: 2018-07-31 14:18:28 INFO: tcp server listening at 0.0.0.0:6443
2018-07-31 14:18:28: 2018-07-31 14:18:28 INFO: running from root user

user

使用Docker镜像跑 SS KCPTUN 客户端已成功，却无法科学

docker run -dt --name ssclient -p 1080:1080 -p 6500:6500/udp mritd/shadowsocks -m "ss-local" -s "-s 127.0.0.1 -p 6500 -b 0.0.0.0 -l 1080 -m aes-256-cfb -k test123 --fast-open" -x -e "kcpclient" -k "-r SERVERIP:6500 -l :6500 -mode fast2"

服务端和测试端，都使用的是这个例子给的。

客户端Docker 日志信息

Starting kcptun......
Starting shadowsocks......
 2018-01-23 18:52:44 INFO: using tcp fast open
 2018-01-23 18:52:44 INFO: initializing ciphers... aes-256-cfb
 2018-01-23 18:52:44 INFO: listening at 0.0.0.0:1080
 2018-01-23 18:52:44 INFO: running from root user
2018/01/23 18:52:44 version: 20171201
2018/01/23 18:52:44 listening on: [::]:6500
2018/01/23 18:52:44 encryption: aes
2018/01/23 18:52:44 nodelay parameters: 1 20 2 1
2018/01/23 18:52:44 remote address: SERVERIP:6500
2018/01/23 18:52:44 sndwnd: 128 rcvwnd: 512
2018/01/23 18:52:44 compression: true
2018/01/23 18:52:44 mtu: 1350
2018/01/23 18:52:44 datashard: 10 parityshard: 3
2018/01/23 18:52:44 acknodelay: false
2018/01/23 18:52:44 dscp: 0
2018/01/23 18:52:44 sockbuf: 4194304
2018/01/23 18:52:44 keepalive: 10
2018/01/23 18:52:44 conn: 1
2018/01/23 18:52:44 autoexpire: 0
2018/01/23 18:52:44 scavengettl: 600
2018/01/23 18:52:44 snmplog:
2018/01/23 18:52:44 snmpperiod: 60
2018/01/23 18:52:44 quiet: false
2018/01/23 18:52:44 connection: 172.17.0.2:45486 -> SERVERIP:6500

服务端Docker 日志信息

Starting kcptun......
Starting shadowsocks......
 2018-01-23 17:59:12 INFO: using tcp fast open
 2018-01-23 17:59:12 INFO: initializing ciphers... aes-256-cfb
 2018-01-23 17:59:12 INFO: tcp server listening at 0.0.0.0:6443
 2018-01-23 17:59:12 INFO: running from root user
2018/01/23 17:59:12 version: 20171201
2018/01/23 17:59:12 listening on: [::]:6500
2018/01/23 17:59:12 target: 127.0.0.1:6443
2018/01/23 17:59:12 encryption: aes
2018/01/23 17:59:12 nodelay parameters: 1 20 2 1
2018/01/23 17:59:12 sndwnd: 1024 rcvwnd: 1024
2018/01/23 17:59:12 compression: true
2018/01/23 17:59:12 mtu: 1350
2018/01/23 17:59:12 datashard: 10 parityshard: 3
2018/01/23 17:59:12 acknodelay: false
2018/01/23 17:59:12 dscp: 0
2018/01/23 17:59:12 sockbuf: 4194304
2018/01/23 17:59:12 keepalive: 10
2018/01/23 17:59:12 snmplog:
2018/01/23 17:59:12 snmpperiod: 60
2018/01/23 17:59:12 pprof: false
2018/01/23 17:59:12 quiet: false

使用SS 客户端连上后，依然无法科学上网

shadowsocks 部分https访问有问题

通过这个镜像提供的代理服务，访问部分https 会有问题。但是我另外一台vps 直接跑在外面的 就正常。

比如访问这个 https://www.okex.com 网站。
这个问题是我在用node 去下载网页的时候发现的 。用curl也会出现这个问题。 提示 server abort ssl handshake。
我用的 proxifier 来设定代理规则。
但是用chrome 通过 proxy switch 插件使用代理就能正常打开。

我怀疑是不是打在镜像里以后 证书环境和外面的不一样 还是经过docker 的nat之后 服务器证书校验严格的 就不会通过。
百思不得其解 。

curl  -v https://www.okex.com
* Rebuilt URL to: https://www.okex.com/
*   Trying 69.171.234.29...
* TCP_NODELAY set
* Connected to www.okex.com (127.0.0.1) port 443 (#0)
* Server aborted the SSL handshake
* Curl_http_done: called premature == 1
* Closing connection 0
curl: (35) Server aborted the SSL handshake

求个镜像

博主你好，请问下，你有centos7 4.9内核的docker镜像吗？谢谢

群晖Docker跑 mritd/shadowsocks 崩溃

如图 不知啥原因,一直没启动成功，先生意外停止。
环境： 群晖上的Docker，映像拉取最新，并在高级设置-》执行命令-》命令 中写入docker run -dt --name ssclient -p 1080:1080 mritd/shadowsocks -m "ss-local" -s "-s 服务器IP -p 服务器端口 -b 0.0.0.0 -l 1080 -m aes-256-cfb -k 服务器密码 --fast-open"

通过php7-fpm的Dockerfile创建镜像总是找不不到docker-php-source

已经将docker-php的所有文件和Dockerfile放在同一目录下，创建时还是报错
/bin/sh: docker-php-source: not found
The command '/bin/sh -c apk upgrade --update && apk ****** /var/cache/apk/' returned a non-zero code: 127
不知是哪里错了，烦请指教，不甚感谢

shadowsocks的docker虽集成了obfs但未提供相关参数

你好！shadowsocks的docker虽集成了obfs但未提供相关参数，麻烦抽空完善，多谢！
https://hub.docker.com/r/mritd/shadowsocks/

shadowsocks新增加的ofbs测试。

docker run --restart=always -d -p 60001:60001 ss/ss -s "-s 0.0.0.0 -p 60001 -m chacha20-ietf-poly1305 -k is*******09 --fast-open --plugin obfs-server --plugin-opts 'obfs=tls'"

貌似命令格式不太对？虽然镜像成功启动了，但是TLS混淆没有开启。小火箭连接，开启TLS混淆连接不上。

Does this image support bbr?

Can't get bbr status using the following command as said by this article:

bash-4.4# sysctl net.ipv4.tcp_available_congestion_control
sysctl: error: 'net.ipv4.tcp_available_congestion_control' is an unknown key
bash-4.4# sysctl net.ipv4.tcp_congestion_control
sysctl: error: 'net.ipv4.tcp_congestion_control' is an unknown key

发现最近 shadwosocks 的 docker 自动退出的很频繁。

docker hub 上的最新版。

能否增加udp模式支持呢？

如题，一些ps4游戏只能走udp模式~

跑docker run 出现以下错误 用latest 的image

V2Ray v3.29 (die Commanderin) 20180705
A unified platform for anti-censorship.
Main: failed to read config file: /etc/v2ray/config.json > Main|Json: failed to execute v2ctl to convert config file. > Command|Platform|CtlCmd: v2ctl doesn't exist > stat /usr/bin/v2ctl: no such file or directory

希望可以client模式可以根据gfwlist.txt自动路由

希望可以client模式可以根据gfwlist.txt自动路由
文档中没有看到跟路由设置相关的信息.

错误日志里很多 "failed to handshake with 124.236.175.174: invalid address type".

在 GCP 上搭建的代理，用的最新的 3.2.0 版本。最近一段时间代理非常不稳定，不知道下面的日志是否正常。

2018-11-13 16:12:13 ERROR: getpeername: Socket not connected
 2018-11-13 16:12:21 ERROR: getpeername: Socket not connected
 2018-11-13 16:12:21 ERROR: getpeername: Socket not connected
 2018-11-13 16:12:22 ERROR: getpeername: Socket not connected
 2018-11-13 16:21:48 ERROR: failed to handshake with 171.34.218.187: invalid address type
 2018-11-13 17:47:14 ERROR: server recv: Connection reset by peer
 2018-11-13 21:20:22 ERROR: failed to handshake with 113.128.105.24: invalid address type
 2018-11-13 22:18:41 ERROR: failed to handshake with 36.47.160.243: invalid address type
 2018-11-13 22:18:47 ERROR: failed to handshake with 112.193.168.180: invalid address type
 2018-11-13 23:34:44 ERROR: server_send_send: Connection reset by peer
 2018-11-13 23:34:48 ERROR: server recv: Connection reset by peer
 2018-11-14 04:11:11 ERROR: failed to handshake with 180.95.225.49: invalid address type
 2018-11-14 09:35:20 ERROR: failed to handshake with 123.145.13.225: invalid host name
 2018-11-14 09:35:21 ERROR: failed to handshake with 113.128.104.49: invalid address type
 2018-11-14 09:35:22 ERROR: failed to handshake with 182.119.196.180: invalid address type
 2018-11-14 09:35:22 ERROR: failed to handshake with 123.144.28.33: invalid address type
 2018-11-14 09:35:23 ERROR: failed to handshake with 112.112.86.209: invalid address type
 2018-11-14 09:35:24 ERROR: fast_open_connect: Address not available
 2018-11-14 09:35:24 ERROR: getpeername: Socket not connected
 2018-11-14 09:35:29 ERROR: fast_open_connect: Address not available
 2018-11-14 09:35:29 ERROR: getpeername: Socket not connected
 2018-11-14 09:38:37 ERROR: failed to handshake with 223.166.75.188: invalid address type
 2018-11-14 09:39:12 ERROR: failed to handshake with 182.119.196.180: invalid address type
 2018-11-14 09:39:13 ERROR: failed to handshake with 113.128.104.49: invalid address type
 2018-11-14 09:40:08 ERROR: fast_open_connect: Address not available
 2018-11-14 09:40:08 ERROR: getpeername: Socket not connected
 2018-11-14 09:40:09 ERROR: failed to handshake with 113.128.104.49: invalid address type
 2018-11-14 09:40:25 ERROR: failed to handshake with 171.34.218.206: invalid address type
 2018-11-14 10:11:56 ERROR: failed to handshake with 106.45.1.221: invalid address type
 2018-11-14 10:12:01 ERROR: failed to handshake with 118.81.226.194: invalid address type
 2018-11-14 10:27:59 ERROR: failed to handshake with 117.89.72.52: invalid address type
 2018-11-14 10:35:44 ERROR: fast_open_connect: Address not available
 2018-11-14 10:35:44 ERROR: getpeername: Socket not connected
 2018-11-14 11:36:54 ERROR: crypto: stream: repeat IV detected
 2018-11-14 11:36:54 ERROR: failed to handshake with 60.1.131.84: authentication error
 2018-11-14 11:47:06 ERROR: failed to handshake with 182.138.162.235: invalid address type
 2018-11-14 11:47:12 ERROR: failed to handshake with 182.138.162.235: invalid address type
 2018-11-14 12:06:10 ERROR: server recv: Connection reset by peer
 2018-11-14 12:07:57 ERROR: failed to handshake with 124.236.175.174: invalid address type
 2018-11-14 12:35:53 ERROR: failed to handshake with 124.235.138.40: invalid address type
 2018-11-14 13:12:00 ERROR: failed to handshake with 123.160.175.183: invalid address type
 2018-11-14 13:16:55 ERROR: failed to handshake with 223.166.75.25: invalid address type
 2018-11-14 13:17:35 ERROR: failed to handshake with 171.34.218.78: invalid address type
 2018-11-14 13:35:20 ERROR: failed to handshake with 180.95.225.206: invalid address type
 2018-11-14 13:35:32 ERROR: remote recv: Connection reset by peer
 2018-11-14 13:51:56 ERROR: fast_open_connect: Address not available
 2018-11-14 13:51:56 ERROR: getpeername: Socket not connected
 2018-11-14 14:29:00 ERROR: remote recv: Connection reset by peer
 2018-11-14 15:35:45 ERROR: failed to handshake with 123.232.225.233: invalid address type
 2018-11-14 15:46:57 ERROR: failed to handshake with 118.81.226.225: invalid address type
 2018-11-14 16:02:04 ERROR: failed to handshake with 223.166.75.167: invalid address type
 2018-11-14 16:11:56 ERROR: failed to handshake with 171.36.132.44: invalid host name
 2018-11-14 16:28:16 ERROR: failed to handshake with 112.117.16.148: invalid address type
 2018-11-14 16:29:54 ERROR: failed to handshake with 116.252.2.109: invalid address type
 2018-11-14 16:43:32 ERROR: failed to handshake with 58.248.200.59: invalid address type
 2018-11-14 17:15:43 ERROR: server recv: Connection reset by peer
 2018-11-14 17:15:46 ERROR: server recv: Connection reset by peer
 2018-11-14 17:31:15 ERROR: server recv: Connection reset by peer

不知道是不是开启了 Proxifier 的 “Resolve hostname through proxy”，但之前没打开的时候也经常不能使用。

另外想问一下，如何禁用掉 ShadowsocksX-NG 的代理规则，只使用 Proxifier 的，两个重复了。尝试过设置 ShadowsocksX-NG 为手动模式，但即便 Proxifier 里添加了 google.com 的域名走代理，还是不能正常访问，只有在自动和全局模式下才行。

Plugin arguments error for simple-obfs client

Hi. I'm using your docker image shadowsocks in a shell script to deploy Shadowsocks server and client. Here is the server script snippet:

# Generate random password...
PASSWORD=$(< /dev/urandom tr -dc _A-Za-z0-9 | head -c${1:-32};echo;)

docker run --name ss-server-80-obfs -idt --network host mritd/shadowsocks -m ss-server -s "-s 0.0.0.0 -p 80 -k $PASSWORD -m chacha20-ietf-poly1305 -u --fast-open --plugin obfs-server --plugin-opts \"obfs=http;failover=127.0.0.1:8080\" -v"

And for client:

SERVER_HOST=$1
PASSWORD=$2

docker run --name ss-local-1080-obfs -idt --network host --restart always mritd/shadowsocks -m ss-local -s "-s $SERVER_HOST -p 80 -l 1080 -k $PASSWORD -m chacha20-ietf-poly1305 -u --fast-open --plugin obfs-local --plugin-opts \"obfs=http;obfs-host=cn.bing.com\" -v"

The client container fails and here's the log:

Kcptun not started......
Starting shadowsocks......
 2017-10-18 17:32:01 INFO: plugin "obfs-local" enabled
 2017-10-18 17:32:01 INFO: using tcp fast open
 2017-10-18 17:32:01 INFO: initializing ciphers... chacha20-ietf-poly1305
 2017-10-18 17:32:01 INFO: udprelay enabled
 2017-10-18 17:32:01 INFO: listening at 127.0.0.1:1080
 2017-10-18 17:32:01 INFO: running from root user

simple-obfs 0.0.3

  maintained by Max Lv <[email protected]>

  usage:

    obfs-local

       -s <server_host>           Host name or IP address of your remote server.
       -p <server_port>           Port number of your remote server.
       -l <local_port>            Port number of your local server.
       --obfs <http|tls>          Enable obfuscating: HTTP or TLS (Experimental).
       --obfs-host <host_name>    Hostname for obfuscating (Experimental).

       [-a <user>]                Run as another user.
       [-f <pid_file>]            The file path to store pid.
       [-t <timeout>]             Socket timeout in seconds.
       [-c <config_file>]         The path to config file.
       [-n <number>]              Max number of open files.
       [-b <local_address>]       Local address to bind.


       [--fast-open]              Enable TCP fast open.
                                  with Linux kernel > 3.7.0.
       [--mptcp]                  Enable Multipath TCP on MPTCP Kernel.

       [-v]                       Verbose mode.
       [-h, --help]               Print this message.

 2017-10-18 17:32:01 ERROR: plugin service exit unexpectedly
 2017-10-18 17:32:01 INFO: closed gracefully

It turns out that the arguments for simple-obfs are passed incorrectly. I tried to remove the quotes:

docker run --name ss-local-1080-obfs -idt --network host --restart always mritd/shadowsocks -m ss-local -s "-s $SERVER_HOST -p 80 -l 1080 -k $PASSWORD -m chacha20-ietf-poly1305 -u --fast-open --plugin obfs-local --plugin-opts obfs=http;obfs-host=cn.bing.com -v"

And it works. But it is strange! As you can see, I escape the quotes when deploying server side and no such error logs appear.

有没有sample如何定义配置一个.yml运行mritd/shadowsocks

想通过 docker stack up -c "${stack_file}" "${stack_name}" 的方式 来运行这个docker mritd/shadowsocks
这里${stack_file}就是.yml的名字，然后${stack_name}则运行的container的名字。
例如：docker stack up -c "./ssr.yml" "ss-server"

请问怎么配置？谢谢！

brook的dockerfile，启动错误。

docker build -t brook/brook ./dockerfile/brook/

docker run --restart=always -d -p 5789:5789 brook/brook "bkserver -l :5789 -p *** -t 10 -m chinaunicom_sales"

用这个命令启动镜像之后，用docker ps -a 查看正在运行的容器，一直显示brook的容器运行错误。

# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e2b197c2e73c brook/brook "./brook ' bkserve..." 6 seconds ago Restarting (3) Less than a second ago jolly_wescoff

是不是命令格式不对？
非常感谢巨巨的辛苦劳动。

mritd/shadowsocks有问题

在arukas.io配置后要不是启动不了，就是启动了后
There is no running container
或者一直变ip和端口，docker没有重启，自己在变很是奇怪

[Proposal] udp2raw and UDPspeeder support

参考来源：
koolshare版梅林固件UDPspeeder和udp2raw串联的完整设置

有没有可能增加 udp2raw 及 udpspeeder 的支持？

我不太确定直接放进 55 目前的容器里是否合适，尽管服务间都是串联，但是也是4个服务(55, kcptun, udp2raw, udpspeeder)了；也许单独跑容器然后用 docker service 的方式把服务 link 起来的方式会更优雅？如果是这样的 kcptun 是否也适合分拆出来？

openshift 怎么应用此镜像？

openshift 如何应用此镜像？cmd 写在哪里？

默认请不要使用 aes-256-cfb

这个已经不安全了，能被监测到流量特征

建议使用新的 aes-256-gcm

使用自定的v2ray config 失败

我试了一下
使用下面的命令，启动起来的v2ray container 可以正常运行。

docker run -dt --name v2ray mritd/v2ray

可是下面的命令，尝试使用自定义的设置（这句话是直接copy @mritd readme里面的那句），container可以创建出来，但是会迅速stop掉。不清楚哪里有问题？

docker run -dt --name v2ray mritd/v2ray -c "{\"log\" : {     \"access\": \"/var/log/v2ray/access.log\",     \"error\": \"/var/log/v2ray/error.log\",     \"loglevel\": \"warning\"   },   \"inbound\": {     \"port\": 4500,     \"protocol\": \"vmess\",     \"settings\": {       \"clients\": [         {           \"id\": \"23ad6b10-8d1a-40f7-8ad0-e3e35cd38297\",           \"level\": 1,           \"alterId\": 64         }       ]     }   },   \"outbound\": {     \"protocol\": \"freedom\",     \"settings\": {}   },   \"outboundDetour\": [     {       \"protocol\": \"blackhole\",       \"settings\": {},       \"tag\": \"blocked\"     }   ], \"routing\": {     \"strategy\": \"rules\",     \"settings\": {       \"rules\": [         {           \"type\": \"field\",           \"ip\": [             \"0.0.0.0/8\",             \"10.0.0.0/8\",             \"100.64.0.0/10\",             \"127.0.0.0/8\",             \"169.254.0.0/16\",             \"172.16.0.0/12\",             \"192.0.0.0/24\",             \"192.0.2.0/24\",             \"192.168.0.0/16\",             \"198.18.0.0/15\",             \"198.51.100.0/24\",             \"203.0.113.0/24\",             \"::1/128\",             \"fc00::/7\",             \"fe80::/10\"           ],           \"outboundTag\": \"blocked\"         }       ]     }   },   \"transport\": {     \"kcpSettings\": {       \"uplinkCapacity\": 10,       \"downlinkCapacity\": 10     }   } }"

update:

1. 为了排除虚拟机的问题，我又重新创建了两台虚拟机（16G内存，8核），container依然无法正常工作。
2. 然后，我把v2ray/official里面的json倒出来，格式化后，按照上面的自定义方法，也无法工作。
   e.g.

docker run -dt --name v2ray -p 8389:8389 mritd/v2ray -c "{\"log\":{\"access\":\"/var/log/v2ray/access.log\",\"error\":\"/var/log/v2ray/error.log\",\"loglevel\":\"warning\"},\"inbound\":{\"port\":10086,\"protocol\":\"vmess\",\"settings\":{\"clients\":[{\"id\":\"23ad6b10-8d1a-40f7-8ad0-e3e35cd38297\",\"level\":1,\"alterId\":64}]}},\"outbound\":{\"protocol\":\"freedom\",\"settings\":{}},\"outboundDetour\":[{\"protocol\":\"blackhole\",\"settings\":{},\"tag\":\"blocked\"}],\"routing\":{\"strategy\":\"rules\",\"settings\":{\"rules\":[{\"type\":\"field\",\"ip\":[\"0.0.0.0/8\",\"10.0.0.0/8\",\"100.64.0.0/10\",\"127.0.0.0/8\",\"169.254.0.0/16\",\"172.16.0.0/12\",\"192.0.0.0/24\",\"192.0.2.0/24\",\"192.168.0.0/16\",\"198.18.0.0/15\",\"198.51.100.0/24\",\"203.0.113.0/24\",\"::1/128\",\"fc00::/7\",\"fe80::/10\"],\"outboundTag\":\"blocked\"}]}}}"

twitter桌面版无法联网，windows版

您好：

我用了shadowsocks后，浏览器上可以翻墙，但是下载的twitter桌面版（windows）不能翻，mac os 又可以。

是什么原因呢？请问怎么解决？

谢谢

请教如何同时监听 ipv4 和ipv6

在原来的版本中，可以通过指定"server":"::"，来达到同时监听ipv4与ipv6的效果，在切换到shadowsocks-libev后，用同样的参数只能监听ipv6，不能监听ipv4。

在普通的用json配置文件的系统中，可以指定"server":["[::0]", "0.0.0.0"]来同时监听ipv6和ipv4，但是在docker中通过参数启动应该如何写-s 后面的字段？

求教arukas.io樱花Docker CMD参数

ss+kcp 在樱花Docker里，CMD详细参数怎么填啊~ 求教。。。

命令是已经用kcptun加速了吗？

docker run -dt --name ss -p 6443:6443 mritd/shadowsocks -s "-s 0.0.0.0 -p 6443 -m chacha20 -k test123 --fast-open"
请问这个命令是已经用kcptun加速了吗？还是说，还要按照其他教程，设置kcptun的加速？

如何配置 ss-manage 管理多用户(多个端口/密码)

查了相关issue以及无法解决，我想在一个vps里配置多个端口对应多个密码

user_config.json里面配置如下
{ "server":"0.0.0.0", "method": "aes-256-cfb", "local_address": "0.0.0.0", "local_port":6443, "port_password": { "8001": "test123", "8002": "test123", "8003": "test123" }, "timeout":600, "fast_open": false }
启动命令：

docker run -dt --name ssserver \ -p 6443:6443 -p 6500:6500/udp -v pwd/user_config.json:/config.json mritd/shadowsocks \ -m "ss-manager" -s "-c /config.json" \

然后在客户端配置8001端口，无法科学上网，请问是我哪里配置有问题吗？
thx

关于shadowsocks镜像请教几个问题

非常感谢你提供这么好的梯子工具，有几个问题请教一下，忘有空解答：

1. 通过参数怎样设置用户名密码；
2. 开启kcptun对客户端有什么要求，官网的客户端是否可以使用kcptun加速；
3. 是否支持json配置文件，如何配置。

请问 docker/shadowsocks 可以设置 timeout 参数吗？

请问怎么样可以设置一个 timeout 参数？

mritd巨巨，求造个轮子。SSRR的dockerfile

https://github.com/shadowsocksrr/shadowsocksr/blob/akkariiin/master/Dockerfile
自从阿卡林接手了SSR之后，创建了akkariiin/master分支。新增加了auth_chain_c和auth_chain_d协议。
不知道他改动了哪里。旧的dockerfile已经不能用了。
求巨巨造个轮子，给我这样刚学会docker的小白，拜谢。

shadowsocks在樱花上运行成功，但仍然无法翻墙

使用环境变量配置

SS_CONFIG = "ss :: -s 0.0.0.0 -p 6443 -m aes-256-cfb -k 666666--fast-open"

cmd留空，启动成功后，shadowsocks客户端启动成功。日志如下

[2017-04-07 10:25:04] Socket connected to ss server: 153.125.233.240:31302
[2017-04-07 10:25:04] connect to clients4.google.com:443
[2017-04-07 10:25:04] Socket connected to ss server: 153.125.233.240:31302
[2017-04-07 10:25:04] connect to clients4.google.com:443

但是浏览器无法连接到网络

无法访问此网站

mail.google.com 意外终止了连接。
请试试以下办法：
检查网络连接
检查代理服务器和防火墙
运行 Windows 网络诊断
ERR_CONNECTION_CLOSED

不知是否跟镜像有关？

请问shadowsocks镜像跑起来之后如何更改端口， VPS 重启后需要再重新跑一遍docker run 吗

谢谢大神的作品

ss最新版的dockerfile是不是命令变了？

root@:~# docker run --restart=always -d -p 6001:6001 ss/ss -s "-s 0.0.0.0 -p 6001 -m chacha20-ietf-poly1305 -k wxz --fast-open --plugin obfs-server --plugin-opts obfs=tls"
f0b43c43b1213c7e***18dc8ecfaab17a86f6ee7ece27c7f
docker: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "exec: "/entrypoint.sh": permission denied".

Please add IPv6 support

Please add IPv6 support, IPv6 is unavailable.