Bug 1329326

Summary:	Mounting /dev in a container causes "PTY allocation request failed on channel 0" on ssh login
Product:	OpenShift Container Platform	Reporter:	Brenton Leanhardt <bleanhar>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED DUPLICATE	QA Contact:	Ma xiaoqiang <xiama>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	amurdaca, aos-bugs, dwalsh, eparis, jokerman, mmccomas, mwysocki, sdodson, trankin, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-22 18:28:28 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:

Description Brenton Leanhardt 2016-04-21 15:45:00 UTC

Description of problem:

In order to use some Kubelet features when running containerized /dev must be mounted in.  However, this appears to break non-root ssh logins and yields a "PTY allocation request failed on channel 0" error.

Version-Release number of selected component (if applicable):

docker-1.9.1-25.el7
openshift v3.2.0.12
kubernetes v1.2.0-36-g4a3f9c5

How reproducible:


Steps to Reproduce:
1. Containerized OSE installation
2. SSH in as non-root

Additional info:

We thought this was fixed in docker 1.9 but it might have been fixed in docker 1.10.  If we don't mount in /dev the Kubelet can not use several storage plugins.

Comment 1 Brenton Leanhardt 2016-04-21 15:49:22 UTC

We talked about this on irc a few weeks ago but failed to formally file a bug.  Do you (or anyone) know if this can be fixed in docker 1.9?

Comment 2 Scott Dodson 2016-04-21 22:30:57 UTC

Treating this as a bug to remove /dev mount from containerized node installation. I've opened https://bugzilla.redhat.com/show_bug.cgi?id=1329423 to ensure docker gets fixed.

Comment 3 Scott Dodson 2016-04-22 18:28:28 UTC

This is being fixed in docker itself so marking this a dupe.

*** This bug has been marked as a duplicate of bug 1329423 ***