2015-09-18 121 views
3

如何避免在这个泊坞窗会话结束时以下错误消息中禁用:为什么mount命令是一个码头工人容器

$ docker run -it ubuntu /bin/bash 
[email protected]:/# ls 
bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var 
[email protected]:/# cd home/ 
[email protected]:/home# ls 
[email protected]:/home# mkdir 1 
[email protected]:/home# mkdir 2 
[email protected]:/home# mount --bind 1 2 
mount: block device /home/1 is write-protected, mounting read-only 
mount: cannot mount block device /home/1 read-only 

更新:

$ docker run --cap-add=SYS_ADMIN -it ubuntu /bin/bash 
[email protected]:/# cd home/ 
[email protected]:/home# mkdir 1 
[email protected]:/home# mkdir 2 
[email protected]:/home# mount --bind 1 2 
mount: block device /home/1 is write-protected, mounting read-only 
mount: cannot mount block device /home/1 read-only 
[email protected]:/home# exit 
$ docker run --cap-add=ALL -it ubuntu /bin/bash 
[email protected]:/# cd home/ 
[email protected]:/home# mkdir 1 
[email protected]:/home# mkdir 2 
[email protected]:/home# mount --bind 1 2 
mount: block device /home/1 is write-protected, mounting read-only 
mount: cannot mount block device /home/1 read-only 
[email protected]:/home# exit 

--privileged是所有虽然。

回答

1

自答案:)使用 '--security-opt apparmor:unconfine d'
禁用的AppArmor会工作。

编号:issue 16429

+0

好的意见。 +1 – VonC

0

尝试按照推荐的issue 9950

你不能调用安装,除非你有CAP_SYS_ADMIN,这是不提供默认容器配置。
你需要docker run --cap-add SYS_ADMIN

+0

然而,这并没有为我工作.. –

+0

又见更新请。 –

相关问题