Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • /home has never been a mount in any namespace. Commented Mar 8, 2017 at 14:14
  • Does that mean you used commands along the lines I suggested? Because "never" is a very strong assertion, my commands wouldn't demonstrate that. I've added a command at the start which would be simpler (and hopefully functional :), and a second speculation on why this might happen based on the result on my system. Commented Mar 8, 2017 at 15:00
  • I found another "broken" machine and your grep command indeed points the finger at NetworkManager. So my "stop NM, rename, restart NM" works, but your grep of mountinfo is what find the culprit. Commented Mar 8, 2017 at 16:22
  • (because /lib/systemd/system/NetworkManager.service uses ProtectHome, at least on the systems we're looking at) Commented Mar 8, 2017 at 16:39