Bug 1468249

Summary:	[docker] Enable knob /proc/sys/fs/may_detach_mounts upon installation
Product:	Red Hat Enterprise Linux 7	Reporter:	Vivek Goyal <vgoyal>
Component:	docker	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED WONTFIX	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	amurdaca, atomic-bugs, dwalsh, ebiederm, jhonce, lsm5, pasik, santiago
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	docker-1.12.6-41.1.gitf55a118.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1441737	Environment:
Last Closed:	2021-01-15 07:39:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1441737
Bug Blocks:	1441743, 1542672

Comment 2 Vivek Goyal 2017-07-06 13:09:23 UTC

runc package drops following file.

/usr/lib/sysctl.d/99-containers.conf

And enables /proc/sys/fs/may_detach_mounts

We need this for docker as well.

By default installing docker does not install runc so this does not get enabled. 

We have two options.

- Either drop similar config file drom docker package.
- Or pull in runc when installing docker.

Hmmm..., may be first one is little light weight solution. So how about dropping another file from docker package says /usr/lib/sysctl.d/99-docker.conf

Comment 3 Vivek Goyal 2017-07-06 13:11:04 UTC

Lokesh, will you be able to take care of this please.

Comment 4 Ed Santiago 2017-07-06 19:20:29 UTC

Confirmed:

   # cat /proc/sys/fs/may_detach_mounts
   0

   # yum install docker
   ...
   Installed:
     docker.x86_64 2:1.12.6-41.1.gitf55a118.el7
   ...
   # cat /proc/sys/fs/may_detach_mounts
   1
   # rpm -q runc
   package runc is not installed

Comment 6 RHEL Program Management 2021-01-15 07:39:23 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.