As you know I was interested in several things that I saw in your configuration, linux works perfectly for me, but I can’t do anything that I know how to do with it, I suppose that you have it to facilitate other functionalities, it doesn’t seem that you have anything configured by whim, or I don’t get to know it. For example, I can’t install any package, or at least I haven’t known how to do it.
I also tried to find out what Shadowsocks is, but I still didn’t have time to learn anything about it, only to understand that I was interested. What did happen to me is that I tried to install the container and when it didn’t start, it stopped immediately, I guess I did something wrong, I share the lines I added.
/interface/veth/add name=veth4 address=192.168.4.5/24 gateway=192.168.4.1 comment=Shadowsocks
/interface/bridge/port add bridge=dockers interface=veth4 comment=Shadowsocks
/container/envs/add name=shadowsocks_envs key=TZ value=“Europe/Madrid”
/container/envs/add name=shadowsocks_envs key=DNS_ADDRS value=192.168.4.2 <---- This is the Pi-Hole veth address
/container/envs/add name=shadowsocks_envs key=PASSWORD value=“xxxxxxx” <---- obviously my password don’t apears
/container/envs/add name=shadowsocks_envs key=SERVER_PORT value=443
/container/envs/add name=shadowsocks_envs key=METHOD value=AEAD_AES_128_GCM
/container/envs/add name=shadowsocks_envs key=ARGS value=“-plugin v2ray-plugin -plugin-opts server;tls;host=xxx;logLevel=none” <---- and I don´t know if “host=xxx” is the problem
/container/mounts/add name=shadowsocks_acme src=nvme1-part1/disk1/shadowsocks/root/acme.sh dst=/root/.acme.sh
/container/mounts/add name=shadowsocks_tmp src=nvme1-part1/disk1/shadowsocks/root/tmp dst=/root/tmp
/container/add remote-image=teddysun/go-shadowsocks2:latest interface=veth4 root-dir=nvme1-part1/disk1/shadowsocks envlist=shadowsocks_envs mounts=shadowsocks_acme,shadowsocks_tmp comment=“[SS] Shadowsocks” workdir=/root dns=192.168.4.2