/dev/pts/ptmx needs to be set to 666

[Steven Dake]

A desktop system becomes unusable after using kolla start because the destop systems depend heavily on the ptmx driver. Recommend force setting the permissions from within the container.

[Imran Hayder (hayderimran7)]

is there any update on this ? i have a temporary fix , which i do like:
stay on same terminal where i deployed kolla. after every container comes up, launch a new terminal fails with permission denied to ptmx issue.
so perform following to get it back working:

$ sudo chmod 777 /dev/pts/ptmx

[Steven Dake (sdake)]

Imran,

We have implemented sudo chmod 777 /dev/pts/ptmx within any container that bindmounts /dev. This appears to solve the problem for me.

Could you confirm master has fixed the problem?

You will have to build all containers on your own (use tools/build.py -t rdo)
Thanks
-steve

[Imran Hayder (hayderimran7)]

Hi Steven, how recently you made and pushed the fix? i just build images yesterday, and started kolla and found the same issue present.
I build my images as :
./tools/build-all-docker-images --tag latest --release

[Steven Dake (sdake)]

Imran,

I'm not sure on the exact date - it was more then 11 days ago. Git blame doesn't work well across renames.

See:

https://github.com/stackforge/kolla/blob/master/docker/common/cinder-app/cinder-volume/config-internal.sh#L87

[Imran Hayder (hayderimran7)]

hmmm...thats strange..isnt that contradictory to what you mentioned..:/ you said you implemented "chmod 777 /dev/pts/ptmx" but the link you posted is setting it as "chmod 666 /dev/pts/ptmx" and thats exactly the cause of issue here.
TL;DR: we need to set chmod 777 for bindmount of /dev but in our recent change we are doing 666 and that makes any terminal rendered as "permission denied" .
thats why i mentioned, that manually changing "chmod 777 /dev/pts/ptmx" fixes the terminal permission .

[Steven Dake (sdake)]

Imran,

It doesn't make my statement contradictory, it makes it incorrect. We set permissions to 666, not 777 for /dev/pts/ptmx which is a file not a directory. I don't see why it would need execute permissions, but perhaps it does. I haven't personally run into this problem. We can go with 777 though, I'll reopen the bug.

[Ryan Hallisey (rthall14)]

Imran,

I don't think we need 777 here. I don't see how /dev/pts/ptmx needs to be
executable since it's default permissions are 666 for root. I've also
tested with 666 for when we mount /dev and it worked fine. The issue in
question is mounting /dev within libvirt will cause problems unless
the proper perms are given to /dev/pts. If it didn't work for you
check the permissions on the host and in the container and make sure
they are 666.

Thanks,
Ryan

[Launchpad Janitor (janitor)]

[Expired for kolla because there has been no activity for 60 days.]