Linux/AM3352: Issue while containerizing networkboot for beaglebone black

Part Number:AM3352

Tool/software: Linux

We want to containerize network boot for beaglebone black based custom board,

So basically we want to start dhcp server, nfs-kernel-server and tftp server on container and attach it to one of the interface on the ubuntu PC. ( Eventually want to make it work on Windows)

I wrote dockerfile with dhcp, nfs-kernel-server, tftpd-hpa and supervisord, all the files are available in below github link,

https://github.com/AnkurTank/bbb_dockerfile_networkboot 

I built it using following command

docker build -f networkboot.dockerfile -t bbb_networkboot

When I run it using following command 

docker run -it --net host --privileged bbb_networkboot

I see following errors and dhcp, nfs doesn't start.

sh-4.3# 2019-03-26 13:34:31,574 CRIT Supervisor running as root (no user in config file)
2019-03-26 13:34:31,576 INFO supervisord started with pid 8
2019-03-26 13:34:32,579 INFO spawned: 'isc-dhcp-server' with pid 12
2019-03-26 13:34:32,581 INFO spawned: 'nfs-kernel-server' with pid 13
2019-03-26 13:34:32,583 INFO spawned: 'rpcbind' with pid 14
2019-03-26 13:34:32,585 INFO spawned: 'xinetd' with pid 15
2019-03-26 13:34:32,587 INFO spawned: 'tftpd-hpa' with pid 17
2019-03-26 13:34:32,665 INFO exited: rpcbind (exit status 0; not expected)
2019-03-26 13:34:32,709 INFO exited: xinetd (exit status 0; not expected)
2019-03-26 13:34:32,741 INFO exited: tftpd-hpa (exit status 0; not expected)
2019-03-26 13:34:32,747 INFO exited: isc-dhcp-server (exit status 1; not expected)
2019-03-26 13:34:32,846 INFO exited: nfs-kernel-server (exit status 0; not expected)
2019-03-26 13:34:33,849 INFO spawned: 'isc-dhcp-server' with pid 82
2019-03-26 13:34:33,851 INFO spawned: 'nfs-kernel-server' with pid 83
2019-03-26 13:34:33,853 INFO spawned: 'rpcbind' with pid 84
2019-03-26 13:34:33,855 INFO spawned: 'xinetd' with pid 85
2019-03-26 13:34:33,857 INFO spawned: 'tftpd-hpa' with pid 86
2019-03-26 13:34:33,863 INFO exited: rpcbind (exit status 1; not expected)
2019-03-26 13:34:33,899 INFO exited: isc-dhcp-server (exit status 1; not expected)
2019-03-26 13:34:33,907 INFO exited: tftpd-hpa (exit status 0; not expected)
2019-03-26 13:34:33,917 INFO exited: xinetd (exit status 0; not expected)
2019-03-26 13:34:33,946 INFO exited: nfs-kernel-server (exit status 0; not expected)
2019-03-26 13:34:35,950 INFO spawned: 'isc-dhcp-server' with pid 145
2019-03-26 13:34:35,952 INFO spawned: 'nfs-kernel-server' with pid 146
2019-03-26 13:34:35,954 INFO spawned: 'rpcbind' with pid 147
2019-03-26 13:34:35,957 INFO spawned: 'xinetd' with pid 148
2019-03-26 13:34:35,959 INFO spawned: 'tftpd-hpa' with pid 149
2019-03-26 13:34:35,966 INFO exited: rpcbind (exit status 1; not expected)
2019-03-26 13:34:36,003 INFO exited: isc-dhcp-server (exit status 1; not expected)
2019-03-26 13:34:36,009 INFO exited: tftpd-hpa (exit status 0; not expected)
2019-03-26 13:34:36,019 INFO exited: xinetd (exit status 0; not expected)
2019-03-26 13:34:36,046 INFO exited: nfs-kernel-server (exit status 0; not expected)
2019-03-26 13:34:39,052 INFO spawned: 'isc-dhcp-server' with pid 208
2019-03-26 13:34:39,054 INFO spawned: 'nfs-kernel-server' with pid 209
2019-03-26 13:34:39,056 INFO spawned: 'rpcbind' with pid 210
2019-03-26 13:34:39,058 INFO spawned: 'xinetd' with pid 211
2019-03-26 13:34:39,061 INFO spawned: 'tftpd-hpa' with pid 212
2019-03-26 13:34:39,071 INFO exited: rpcbind (exit status 1; not expected)
2019-03-26 13:34:39,097 INFO gave up: rpcbind entered FATAL state, too many start retries too quickly
2019-03-26 13:34:39,098 INFO exited: isc-dhcp-server (exit status 1; not expected)
2019-03-26 13:34:39,099 INFO gave up: isc-dhcp-server entered FATAL state, too many start retries too quickly
2019-03-26 13:34:39,111 INFO exited: tftpd-hpa (exit status 0; not expected)
2019-03-26 13:34:39,119 INFO gave up: tftpd-hpa entered FATAL state, too many start retries too quickly
2019-03-26 13:34:39,120 INFO exited: xinetd (exit status 0; not expected)
2019-03-26 13:34:39,151 INFO gave up: xinetd entered FATAL state, too many start retries too quickly
2019-03-26 13:34:39,151 INFO exited: nfs-kernel-server (exit status 0; not expected)
2019-03-26 13:34:40,152 INFO gave up: nfs-kernel-server entered FATAL state, too many start retries too quickly

Any suggestion/pointers to this problem.

I have posted this question on docker forum at below link as well, however I have used e2e forum more and may be someone already did it for beaglebone black what I am trying to do so asking it here.

https://forums.docker.com/t/setting-up-network-boot-in-docker-container/71937

Thanks in advance!