2015-09-18 75 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

又見更新請。 –

相關問題