I am also on the same boat, I have DL2100 and tried several time. I am trying to setup OwnCloud. May be if I try with stock docker it will work. I will PM you and let you know my finding. I am also on path to start fresh.
1 Like
I compiled the kernel from source for PR4100 and installed the 3 modules you mentioned. The overlay networks are being created successfully and I can run services on them without a problem but when I publish a port on the ingress network I can’t access the service using the NAS ip address (I tried both with curl from the NAS itself and from another computer). When I do the same thing on my desktop pc (on a separate single-node swarm cluster) it works fine and I can access the service without a problem.
Any ideas what might be the issue with this? One example service I’m creating is:
docker service create --name foobar --publish 8000:80 nginx
EDIT:
Ok, turns out it’s the routing mesh that doesn’t work which is not a huge issue for me as I’m planning to use this as a single node swarm. So to resolve this I created my services with the dnsrr endpoint-mode and published the ports directly on the swarm node instead of the ingress network. For example the above would become:
docker service create --name foobar --endpoint-mode dnsrr --publish mode=host,target=80,published=8000 nginx
Curious if there are any good tutorials for getting this running on a PR2100. I’d like to host my own Bitwarden server, and I’m not a Linux pro. Many of the instructions here I’m not quite following from a where to start perspective. I installed the Docker bin file on my NAS, but from there what steps to take to actually get Bitwarden up and running are a mystery to me. Any guidance would be appreciated. Thanks!
I installed docker compose following this guide I do have some issues and able to get around them. However, what I’m finding is after my NAS restarts or the power goes out (I live in an apartment) I lose my docker images, configurations (in /var/lib/), docker compose and the permissions I’ve set on the folders. Any advice?
Did you figure this one out? I think I’m having a similar issue where my torrents are only stored within the container’s image instead of the physical filesystem
Hello,
I have a problem to start the dockerd daemon. Here is the output from my terminal window:
Blockquote
root@WDMyCloud docker # docker -v
Docker version 19.03.2, build 6a30dfc
root@WDMyCloud docker # dockerd -D
INFO[2020-06-22T15:56:19.703372840-07:00] Starting up
WARN[2020-06-22T15:56:19.723269640-07:00] could not change group /var/run/docker.sock to docker: group docker not found
DEBU[2020-06-22T15:56:19.724116080-07:00] Listener created for HTTP on unix (/var/run/docker.sock)
WARN[2020-06-22T15:56:19.725204400-07:00] unable to modify root key limit, number of containers could be limited by this quota: open /proc/sys/kernel/keys/root_maxkeys: no such file or directory
DEBU[2020-06-22T15:56:19.727195440-07:00] Golang’s threads limit set to 7110
INFO[2020-06-22T15:56:19.729337000-07:00] parsed scheme: “unix” module=grpc
INFO[2020-06-22T15:56:19.729552200-07:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2020-06-22T15:56:19.729814360-07:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 }] } module=grpc
INFO[2020-06-22T15:56:19.730016400-07:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2020-06-22T15:56:19.730516520-07:00] pickfirstBalancer: HandleSubConnStateChange: 0x3d75880, CONNECTING module=grpc
INFO[2020-06-22T15:56:19.730732280-07:00] blockingPicker: the picked transport is not ready, loop back to repick module=grpc
WARN[2020-06-22T15:56:39.731319120-07:00] grpc: addrConn.createTransport failed to connect to {unix:///run/containerd/containerd.sock 0 }: didn’t receive server preface in time. Reconnecting… module=grpc
INFO[2020-06-22T15:56:39.731667360-07:00] pickfirstBalancer: HandleSubConnStateChange: 0x3d75880, TRANSIENT_FAILURE module=grpc
DEBU[2020-06-22T15:56:39.732372720-07:00] Cleaning up old mountid : start.
failed to start daemon: failed to dial “/run/containerd/containerd.sock”: all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake: unavailable
root@WDMyCloud docker #
Blockquote
Can someone help how to resolve this?
Thank you in advance
i cant connect to port 9000 it says " refused to connect"
Hi,
I’ve just been looking at this and I am wondering if there is something recently that changed with new firmware updates from WD that has broken this functionality, as I am also getting the same thing with docker 19.03.8. I also found that when trying to build the new version of docker (19.03.12) on the WD EX4100, that the network within the containers was not connecting either, so something appears to have changed. I’ll keep investigating and if I find anything will share to the group.
Cheers,
JediNite
Hi all,
I have done some more digging on this and it looks like for some reason the docker bridging is busted. I have tried going back several firmware versions of the EX4100 in case something was changed in there but it made no difference. I also tried using docker 19.03.8 and 19.03.07 as these were some of the most recent builds I had and this made no difference. I also tried recreating the “_docker” directory and portainer directories from scratch and again made no difference. All the kernel settings to allow bridging to work look correct and also the iptables rules look correct. The recommendation from docker is to now use a custom bridge network and bind containers to these instead of the default bridge network however this also seems to make no difference (Use bridge networks | Docker Documentation).
So not sure what else to try and restore this functionality at this point.
EDIT: I forgot to mention that if you change the portainer docker container to use the “host” network, it works as expected, so the issue is definitely with the NAT / Bridging layer. Command to do this is below:
docker run -d --network="host" -p 8000:8000 -p 9000:9000 --restart always --name portainer -v /var/run/docker.sock:/var/run/docker.sock -v /mnt/HD/HD_a2/Nas_Prog/docker/portainer:/data portainer/portainer
Cheers,
JediNite
2 Likes
I just created an account to say @JediNite you make my day.
For anyone having a “refused to connect”, you can workaround it doing:
- Enable SSH (Enable SSH Doc link)
For the Ex2Ultra is in Settings/Network - Access the NAS by SSH using PuTTY for example (user: sshd and the password)
- Run the JediNite Command
- Access the http://<IP_NAS>:9000 to use portainer
Enjoy
1 Like
Hi all,
Okay, so I think here is the root of the problem. I downloaded the GPL Source Code package and ran the “check_config.sh” script referenced here :
root@WDMyCloudEX4100 Public # ./check-config.sh ./WDMyCloud_EX4100_GPL_v2.40.155_20200713/kernel/linux-3.10.39-2014_T3.0/linux-3.10.39-2014_T3.0_YY/.config
info: reading kernel config from ./WDMyCloud_EX4100_GPL_v2.40.155_20200713/kernel/linux-3.10.39-2014_T3.0/linux-3.10.39-2014_T3.0_YY/.config ...
Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: missing
- CONFIG_VETH: enabled
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled
- CONFIG_NF_NAT_IPV4: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: missing
- CONFIG_IP_NF_NAT: missing
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_NF_NAT_NEEDED: enabled
- CONFIG_POSIX_MQUEUE: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
Optional Features:
- CONFIG_USER_NS: missing
- CONFIG_SECCOMP: missing
- CONFIG_CGROUP_PIDS: missing
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
(cgroup swap accounting is currently enabled)
- CONFIG_MEMCG_KMEM: missing
- CONFIG_RESOURCE_COUNTERS: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: missing
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_CFQ_GROUP_IOSCHED: missing
- CONFIG_CGROUP_PERF: missing
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: missing
- CONFIG_NETPRIO_CGROUP: missing
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: missing
- CONFIG_IP_VS: missing
- CONFIG_IP_VS_NFCT: missing
- CONFIG_IP_VS_RR: missing
- CONFIG_EXT3_FS: enabled
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: missing
- CONFIG_EXT3_FS_SECURITY: missing
(enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
- "overlay":
- CONFIG_VXLAN: missing
Optional (for encrypted networks):
- CONFIG_CRYPTO: enabled
- CONFIG_CRYPTO_AEAD: missing
- CONFIG_CRYPTO_GCM: missing
- CONFIG_CRYPTO_SEQIV: missing
- CONFIG_CRYPTO_GHASH: missing
- CONFIG_XFRM: enabled
- CONFIG_XFRM_USER: missing
- CONFIG_XFRM_ALGO: missing
- CONFIG_INET_ESP: missing
- CONFIG_INET_XFRM_MODE_TRANSPORT: enabled
- "ipvlan":
- CONFIG_IPVLAN: missing
- "macvlan":
- CONFIG_MACVLAN: enabled
- CONFIG_DUMMY: missing
- "ftp,tftp client in container":
- CONFIG_NF_NAT_FTP: missing
- CONFIG_NF_CONNTRACK_FTP: missing
- CONFIG_NF_NAT_TFTP: missing
- CONFIG_NF_CONNTRACK_TFTP: missing
- Storage Drivers:
- "aufs":
- CONFIG_AUFS_FS: missing
- "btrfs":
- CONFIG_BTRFS_FS: enabled (as module)
- CONFIG_BTRFS_FS_POSIX_ACL: missing
- "devicemapper":
- CONFIG_BLK_DEV_DM: enabled
- CONFIG_DM_THIN_PROVISIONING: enabled
- "overlay":
- CONFIG_OVERLAY_FS: missing
- "zfs":
- /dev/zfs: missing
- zfs command: missing
- zpool command: missing
Limits:
cat: can't open '/proc/sys/kernel/keys/root_maxkeys': No such file or directory
./check-config.sh: line 347: [: -le: unary operator expected
cat: can't open '/proc/sys/kernel/keys/root_maxkeys': No such file or directory
- /proc/sys/kernel/keys/root_maxkeys:
If you look over the listing there are a few key kernel settings that do not appear to be enabled:
- CONFIG_KEYS: missing
- CONFIG_NETFILTER_XT_MATCH_IPVS: missing
- CONFIG_IP_NF_NAT: missing
The last one in particular does this: “This enables the `nat’ table in iptables. This allows masquerading, port forwarding and other forms of full Network Address Port Translation.”
Without this one enabled, docker in bridge mode will never work as NAT is critical for this to function. To fix this one would need to build a custom kernel and firmware image with this enabled. I am not sure if this is a setting that was changed recently, and not had time to look more.
So looks like using “host” network mode is the only way to use docker at least for now.
Cheers,
JediNite
1 Like
Thanks for the investigation. It might be possible to get these features as a module, but let’s fix it in the base installer.
I’m about to rework the repo a bit anyway for the OS5 update. It has a recent kernel and if missing I’ll request them to add it.
Hi all,
I may have stumbled on the fix for network bridging issue.
Update the following line in /mnt/HD/HD_a2/Nas_Prog/docker/daemon.sh from:
${DOCKERD} -D >> /var/lib/docker/docker.log 2>&1 &
to
${DOCKERD} -D --ip-masq=true >> /var/lib/docker/docker.log 2>&1 &
It looks like somewhere along the line the default for the “ip-masq” setting compiled in the docker daemon was changed from true to false, so overriding it at start time fixes the issue.
@Tfl - Can we get this put into the upstream package on wdcommunity ? I am not sure what WD models this might be relevant for.
Cheers,
JediNite
1 Like
And I’ll remove the debug logging while at it 
This fix is much better than using host network for all containers.
I’m still struggling with the non-working docker bridge mode.
--ip-masq=true or user defined networks has not resolved the busted docker bridge issue on my “My Cloud EX2 Ultra” (latest firmware 2.40.155, docker 19.03.8). I’ve tried several docker compose yml network definition combinations (e.g. external predefined). I’ve also checked IpTables etc. and it seems correct.
I’m running Portainer in Host mode which I would also like to change due changing Twonky Server Port makes much more effort (changing config file is not sufficient due auto startup of twonkey has port 9000 as cmd param which in turn means dangerous change of a boot autostart file is required).
Do I really need to factory reset/wipe the storage and start again by e.g. installing docker as first app? @JediNite: Do you have some further approaches to solve this issue?
Many thanks in advance.
I spent quite a bit of time looking at the issue on my EX4100 and that was the solution that worked for me (and it was very obscure to track down). Nothing else really comes to mind in looking at what to check if the rest of the config of your NAS is stock standard and you are using the packages supplied. I’ve not used an EX2 Ultra before so don’t have access to test anything out 
Is the EX2 an “arm” or “x86” based NAS ? If it is arm based, you could try and compile your own docker on it and see if it works better. I have some instructions at my github page for the EX4100, so these may work for your NAS.
Cheers,
JediNite
Thanks @JediNite
I will give it a try if no one else has a clue how to solve IT otherwise.
Therefore the question to all: Has anybody with a EX2 Ultra and official firmware running docker 19.03.8 with working bridge mode?
Let’s give it another shot: on a EX2Ultra platform, please provide the following
Available kernel modules
ls /usr/local/modules/driver
Loaded kernel modules (when docker should be running)
lsmod
Logs (not the boot part, just the part when running docker init.sh)
dmesg
This is what I have on PR4100
root@mycloud driver # ls /usr/local/modules/driver
async_memcpy.ko grace.ko msdos.ko nls_cp850.ko tunnel6.ko
async_pq.ko hfs.ko netatop.ko nls_iso8859-1.ko udf.ko
async_raid6_recov.ko ip6_tables.ko nf_conntrack.ko nls_iso8859-2.ko ufsd.ko
async_tx.ko ip6_tunnel.ko nf_conntrack_ipv4.ko nls_utf8.ko vfat.ko
async_xor.ko ip6table_filter.ko nf_conntrack_ipv6.ko pstore.ko x_tables.ko
bonding.ko ip_tables.ko nf_defrag_ipv4.ko quota_tree.ko xfrm6_mode_beet.ko
br_netfilter.ko ip_tunnel.ko nf_defrag_ipv6.ko quota_v2.ko xfrm6_mode_transport.ko
bridge.ko ipt_MASQUERADE.ko nf_log_common.ko raid0.ko xfrm6_mode_tunnel.ko
cifs.ko iptable_filter.ko nf_log_ipv4.ko raid1.ko xfs.ko
dm-bio-prison.ko iptable_nat.ko nf_log_ipv6.ko raid10.ko xor.ko
dm-bufio.ko ipv6.ko nf_nat.ko raid456.ko xt_LOG.ko
dm-crypt.ko iscsi_target_mod.ko nf_nat_ipv4.ko raid6_pq.ko xt_addrtype.ko
dm-mod.ko iscsi_tcp.ko nf_nat_masquerade_ipv4.ko scsi_transport_iscsi.ko xt_conntrack.ko
dm-persistent-data.ko isofs.ko nfs.ko sit.ko xt_limit.ko
dm-snapshot.ko jnl.ko nfs_acl.ko stp.ko xt_nat.ko
dm-thin-pool.ko libiscsi.ko nfsd.ko sunrpc.ko xt_recent.ko
exportfs.ko libiscsi_tcp.ko nfsv2.ko target_core_file.ko xt_state.ko
fat.ko linear.ko nfsv3.ko target_core_mod.ko xt_tcpudp.ko
fscache.ko llc.ko nls_ascii.ko tun.ko
fuse.ko lockd.ko nls_cp437.ko tunnel4.ko
root@mycloud driver # /usr/bin/lsmod
Module Size Used by
br_netfilter 28672 0
bridge 131072 1 br_netfilter
stp 16384 1 bridge
llc 16384 2 bridge,stp
iptable_nat 16384 1
ipt_MASQUERADE 16384 2
nf_nat_masquerade_ipv4 16384 1 ipt_MASQUERADE
xt_nat 16384 1
xt_addrtype 16384 2
nf_nat_ipv4 16384 1 iptable_nat
nf_nat 28672 3 xt_nat,nf_nat_masquerade_ipv4,nf_nat_ipv4
em28xx_dvb 32768 0
cx231xx_dvb 20480 0
cx231xx_alsa 16384 0
cx231xx 180224 2 cx231xx_alsa,cx231xx_dvb
em28xx_alsa 24576 0
em28xx 98304 2 em28xx_dvb,em28xx_alsa
mxl692 20480 0
m88ds3103 28672 0
ts2020 20480 0
a8293 16384 0
lgdt3306a 32768 0
si2168 20480 0
si2157 20480 0
cx25840 73728 0
cx2341x 32768 1 cx231xx
videobuf2_v4l2 28672 1 cx231xx
videobuf2_dvb 16384 0
dvb_core 139264 4 m88ds3103,videobuf2_dvb,cx231xx_dvb,em28xx_dvb
videobuf2_vmalloc 16384 2 dvb_core,cx231xx
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_common 57344 4 videobuf2_dvb,dvb_core,cx231xx,videobuf2_v4l2
tveeprom 24576 2 em28xx,cx231xx
videobuf_vmalloc 16384 0
videobuf_core 32768 1 videobuf_vmalloc
videodev 229376 7 cx2341x,videobuf2_common,cx231xx_alsa,em28xx,cx231xx,videobuf2_v4l2,cx25840
mc 45056 8 videobuf2_common,videodev,em28xx,dvb_core,cx231xx,videobuf2_v4l2,si2157,cx25840
frame_vector 16384 2 videobuf2_vmalloc,videobuf2_memops
i2c_mux 16384 4 m88ds3103,si2168,cx231xx,lgdt3306a
snd_pcm 110592 2 cx231xx_alsa,em28xx_alsa
snd_timer 36864 1 snd_pcm
snd 69632 4 cx231xx_alsa,snd_timer,em28xx_alsa,snd_pcm
soundcore 16384 1 snd
netatop 69632 0
iscsi_tcp 20480 0
libiscsi_tcp 24576 1 iscsi_tcp
libiscsi 57344 2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi 102400 3 libiscsi,iscsi_tcp
nf_log_ipv6 16384 1
nf_conntrack_ipv6 16384 2
nf_defrag_ipv6 32768 1 nf_conntrack_ipv6
ip6table_filter 16384 1
ip6_tables 24576 1 ip6table_filter
nf_log_ipv4 16384 1
nf_conntrack_ipv4 16384 7
nf_defrag_ipv4 16384 1 nf_conntrack_ipv4
iptable_filter 16384 1
ip_tables 24576 2 iptable_filter,iptable_nat
xt_limit 16384 2
nf_log_common 16384 2 nf_log_ipv6,nf_log_ipv4
xt_LOG 16384 2
xt_recent 20480 4
xt_tcpudp 16384 7
xt_state 16384 0
xt_conntrack 16384 5
nf_conntrack 94208 9 xt_state,xt_nat,nf_conntrack_ipv6,nf_conntrack_ipv4,ipt_MASQUERADE,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
x_tables 40960 13 xt_state,xt_LOG,xt_nat,ip_tables,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_recent,ip6table_filter,xt_addrtype,xt_conntrack,ip6_tables
rstbtn 16384 0
bonding 139264 0
xfrm6_mode_tunnel 16384 0
xfrm6_mode_transport 16384 0
xfrm6_mode_beet 16384 0
ip6_tunnel 32768 0
tunnel6 16384 1 ip6_tunnel
sit 24576 0
ip_tunnel 24576 1 sit
tunnel4 16384 1 sit
ipv6 425984 80 nf_conntrack_ipv6,sit,xfrm6_mode_tunnel,xfrm6_mode_beet,nf_defrag_ipv6,ip6_tunnel,bridge
tun 36864 0
ufsd 737280 0
jnl 36864 1 ufsd
cifs 430080 0
xfs 757760 0
udf 98304 0
quota_v2 16384 2
quota_tree 20480 1 quota_v2
pstore 24576 0
nls_utf8 16384 0
nls_iso8859_2 16384 0
nls_iso8859_1 16384 0
nls_cp850 20480 0
nls_cp437 20480 0
nls_ascii 16384 0
nfsd 122880 11
nfsv3 36864 0
nfsv2 24576 0
nfs 180224 2 nfsv2,nfsv3
lockd 90112 4 nfsd,nfsv2,nfs,nfsv3
grace 16384 1 lockd
nfs_acl 16384 1 nfsd
isofs 45056 0
hfs 65536 0
fuse 114688 0
fscache 57344 1 nfs
vfat 20480 0
msdos 20480 0
exportfs 16384 2 nfsd,xfs
fat 77824 2 msdos,vfat
raid456 131072 0
raid10 57344 0
raid1 40960 1
raid0 20480 0
linear 16384 0
dm_thin_pool 77824 0
dm_persistent_data 77824 1 dm_thin_pool
dm_snapshot 45056 0
dm_crypt 40960 0
dm_bufio 32768 2 dm_persistent_data,dm_snapshot
dm_bio_prison 20480 1 dm_thin_pool
dm_mod 131072 4 dm_bufio,dm_crypt,dm_thin_pool,dm_snapshot
sunrpc 262144 16 nfsd,nfsv2,nfs_acl,lockd,nfs,nfsv3
async_raid6_recov 20480 1 raid456
async_pq 16384 2 raid456,async_raid6_recov
async_memcpy 16384 2 raid456,async_raid6_recov
async_xor 16384 3 async_pq,raid456,async_raid6_recov
async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov
xor 24576 1 async_xor
raid6_pq 122880 3 async_pq,raid456,async_raid6_recov
Hello!
On my ex2:
root@MyCloudEX2Ultra root # ls /usr/local/modules/driver
bonding.ko ipip.ko jnl.ko nf_conntrack_ipv6.ko stp.ko ufsd.ko xt_conntrack.ko
bridge.ko ipt_MASQUERADE.ko libiscsi.ko nf_defrag_ipv4.ko target_core_file.ko x_tables.ko xt_limit.ko
btrfs.ko iptable_filter.ko libiscsi_tcp.ko nf_defrag_ipv6.ko target_core_iblock.ko xfrm6_mode_beet.ko xt_nat.ko
ip6_tables.ko iptable_nat.ko llc.ko nf_nat.ko target_core_mod.ko xfrm6_mode_transport.ko xt_recent.ko
ip6_tunnel.ko ipv6.ko netatop.ko nf_nat_ipv4.ko tun.ko xfrm6_mode_tunnel.ko xt_state.ko
ip6table_filter.ko iscsi_target_mod.ko nf_conntrack.ko scsi_transport_iscsi.ko tunnel4.ko xt_LOG.ko xt_tcpmss.ko
ip_tables.ko iscsi_tcp.ko nf_conntrack_ipv4.ko sit.ko tunnel6.ko xt_addrtype.ko xt_tcpudp.ko
root@MyCloudEX2Ultra root # lsmod
Module Size Used by
bridge 79157 0
stp 1355 1 bridge
llc 3238 2 bridge,stp
iptable_nat 2265 1
ipt_MASQUERADE 1400 1
xt_nat 1425 0
xt_addrtype 2382 2
nf_nat_ipv4 3032 1 iptable_nat
nf_nat 10763 4 iptable_nat,ipt_MASQUERADE,xt_nat,nf_nat_ipv4
netatop 34391 0
iscsi_tcp 8235 0
libiscsi_tcp 11152 1 iscsi_tcp
libiscsi 30702 2 iscsi_tcp,libiscsi_tcp
scsi_transport_iscsi 47383 3 iscsi_tcp,libiscsi
nf_conntrack_ipv6 6045 2
nf_defrag_ipv6 13685 1 nf_conntrack_ipv6
ip6table_filter 1047 1
ip6_tables 10114 1 ip6table_filter
nf_conntrack_ipv4 5721 4
nf_defrag_ipv4 967 1 nf_conntrack_ipv4
iptable_filter 1103 1
ip_tables 9834 2 iptable_nat,iptable_filter
xt_tcpmss 1106 2
xt_limit 1345 2
xt_LOG 11167 2
xt_recent 7713 4
xt_tcpudp 1884 6
xt_state 985 0
xt_conntrack 2647 5
nf_conntrack 44228 8 iptable_nat,ipt_MASQUERADE,nf_nat_ipv4,nf_nat,nf_conntrack_ipv6,nf_conntrack_ipv4,xt_state,xt_conntrack
x_tables 11829 14 ipt_MASQUERADE,xt_nat,xt_addrtype,ip6table_filter,ip6_tables,iptable_filter,ip_tables,xt_tcpmss,xt_limit,xt_LOG,xt_recent,xt_tcpudp,xt_state,xt_conntrack
xfrm6_mode_tunnel 1421 0
xfrm6_mode_transport 1035 0
xfrm6_mode_beet 1451 0
ip6_tunnel 15874 0
tunnel6 1952 1 ip6_tunnel
tunnel4 2127 0
ipv6 262497 47 bridge,nf_conntrack_ipv6,nf_defrag_ipv6,xfrm6_mode_tunnel,xfrm6_mode_beet,ip6_tunnel
tun 17281 2
btrfs 726709 0
ufsd 659237 0
jnl 27361 1 ufsd
root@MyCloudEX2Ultra root # dmesg
[ 62.972465] Bridge firewalling registered
[ 66.835183] device veth75eb352 entered promiscuous mode
[ 66.839633] IPv6: ADDRCONF(NETDEV_UP): veth75eb352: link is not ready
[ 67.541294] cgroup: runc (6259) created nested cgroup for controller “blkio” which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[ 68.473808] IPv6: ADDRCONF(NETDEV_CHANGE): veth75eb352: link becomes ready
[ 68.479447] docker0: port 1(veth75eb352) entered forwarding state
[ 68.484284] docker0: port 1(veth75eb352) entered forwarding state
[ 83.522126] docker0: port 1(veth75eb352) entered forwarding state
[ 1682.085269] device veth6794e1c entered promiscuous mode
[ 1682.089392] IPv6: ADDRCONF(NETDEV_UP): veth6794e1c: link is not ready
[ 1682.094576] docker0: port 2(veth6794e1c) entered forwarding state
[ 1682.099406] docker0: port 2(veth6794e1c) entered forwarding state
[ 1682.104285] docker0: port 2(veth6794e1c) entered disabled state
[ 1683.523829] IPv6: ADDRCONF(NETDEV_CHANGE): veth6794e1c: link becomes ready
[ 1683.529492] docker0: port 2(veth6794e1c) entered forwarding state
[ 1683.534333] docker0: port 2(veth6794e1c) entered forwarding state
[ 1698.562126] docker0: port 2(veth6794e1c) entered forwarding state
[ 3061.817599] device veth77f7797 entered promiscuous mode
[ 3061.821864] IPv6: ADDRCONF(NETDEV_UP): veth77f7797: link is not ready
[ 3061.827070] docker0: port 3(veth77f7797) entered forwarding state
[ 3061.831906] docker0: port 3(veth77f7797) entered forwarding state
[ 3061.836840] docker0: port 3(veth77f7797) entered disabled state
[ 3063.453263] IPv6: ADDRCONF(NETDEV_CHANGE): veth77f7797: link becomes ready
[ 3063.458922] docker0: port 3(veth77f7797) entered forwarding state
[ 3063.463774] docker0: port 3(veth77f7797) entered forwarding state
[ 3063.952600] docker0: port 3(veth77f7797) entered disabled state
[ 3063.959101] device veth77f7797 left promiscuous mode
[ 3063.962822] docker0: port 3(veth77f7797) entered disabled state
[ 3223.452529] docker0: port 1(veth75eb352) entered disabled state
[ 3223.592519] docker0: port 1(veth75eb352) entered disabled state
[ 3223.598998] device veth75eb352 left promiscuous mode
[ 3223.602715] docker0: port 1(veth75eb352) entered disabled state
[ 3713.622543] docker0: port 2(veth6794e1c) entered disabled state
[ 3713.772562] docker0: port 2(veth6794e1c) entered disabled state
[ 3713.779055] device veth6794e1c left promiscuous mode
[ 3713.782772] docker0: port 2(veth6794e1c) entered disabled state
[57443.744547] device vethc7cacab entered promiscuous mode
[57443.748848] IPv6: ADDRCONF(NETDEV_UP): vethc7cacab: link is not ready
[57446.063733] IPv6: ADDRCONF(NETDEV_CHANGE): vethc7cacab: link becomes ready
[57446.069389] docker0: port 1(vethc7cacab) entered forwarding state
[57446.074252] docker0: port 1(vethc7cacab) entered forwarding state
[57446.862602] docker0: port 1(vethc7cacab) entered disabled state
[57446.869075] device vethc7cacab left promiscuous mode
[57446.872823] docker0: port 1(vethc7cacab) entered disabled state
[57799.771377] device veth035f758 entered promiscuous mode
[57799.775699] IPv6: ADDRCONF(NETDEV_UP): veth035f758: link is not ready
[57801.623721] IPv6: ADDRCONF(NETDEV_CHANGE): veth035f758: link becomes ready
[57801.629342] docker0: port 1(veth035f758) entered forwarding state
[57801.634178] docker0: port 1(veth035f758) entered forwarding state
[57802.572562] docker0: port 1(veth035f758) entered disabled state
[57802.579089] device veth035f758 left promiscuous mode
[57802.582789] docker0: port 1(veth035f758) entered disabled state
root@MyCloudEX2Ultra root #
Hi all,
I just tried installing OS5 on my EX4100 and it has completely broken docker. The OS5 release has no base docker installed in it anymore and I am trying to install it manually, however when trying to start a container get a message about “mqueue” not being mounted. If I try to mount a mqueue filesysytem into /dev/mqueue, I get a message indicating it is an unknown filesystem type. I am guessing that “CONFIG_POSIX_MQUEUE” is not supported in the shipped kernel, but have no way to verify.
So as an FYI, if you are using docker in anger on these units, DON’T upgrade to OS5 as you will lose all docker functionality.
Cheers,
JediNite
