Filippo Squillace

Thanks @PkmX; that seems really to be a good workaround as it generate the `locale-archive` file. ```sh >> ll ${JUNEST_HOME}/usr/lib/locale/locale-archive ls: cannot access '/home/feel/.junest/usr/lib/locale/locale-archive': No such file or directory >>...

I have tried installing and using `neovim` using CentOS 7 and just work. I cannot try with CentOS 6.9 though. Please if you find any way to fix it, share...

Thanks I was able to reproduce the problem. Maybe one way would be to compile proot from source and change junest code to point to the new compiled proot.

Hey @joernhees Thanks for this change! (and sorry for the delay, there are too many projects to deal with lately :smile:) I just want to give you more context about...

In systems with many names in LDAP it takes to me a negligible amount of time. So, I guess the fact that it is slow in you case might be...

Never explored such possibility. I guess it will not be easy as docker would require kernel dependencies which are accessible only by being a real root. Maybe using the Linux...

Good news! I run provisioned machines in Vagrant on multiple Linux Distros. The user namespace is enabled on most of the distros: ### Archlinux Works great! Linux archlinux 5.2.5-arch1-1-ARCH #1...

Hi all, So, this is related to a very old issue: https://github.com/fsquillace/junest/issues/161 When updating `glibc` there are multiple problems with `proot`. If by any chance you can use Linux user...

BTW I have updated the JuNest image with the latest version. I will try to make sure to update it every 3 months from now.

You got some error with `getent` too which is weird. You might have permission issues there. Can you try `junest -f`?