CleanHit

Results 17 comments of CleanHit

Sleeping for 1 second to let systemd settle nsenter: cannot open /proc/25/ns/time: No such file or directory

Same here

Sleeping for 1 second to let systemd settle nsenter: cannot open /proc/25/ns/time: No such file or directory

@lyh2048 https://github.com/DamionGans/ubuntu-wsl2-systemd-script/issues/76#issuecomment-1122717349

Ubuntu 22.04 LTS nsenter: cannot open /proc/xxx/ns/time: No such file or directory

Having the same problem after upgrading Ubuntu WSL from 20.04 to 22.04.

Ubuntu 22.04 LTS nsenter: cannot open /proc/xxx/ns/time: No such file or directory

@c01hl going into my WSL2 Ubuntu 22.04 with `wsl -e bash --norc` command and using this https://github.com/DamionGans/ubuntu-wsl2-systemd-script/issues/36#issuecomment-732090101 to edit the file using `sudo nano /usr/sbin/enter-systemd-namespace` helped me to fix my...

Ubuntu 22.04 LTS nsenter: cannot open /proc/xxx/ns/time: No such file or directory

@apos this is weird. I logged in using `wsl -e bash --norc` under PowerShell, then I only did the `-m -p` change from https://github.com/DamionGans/ubuntu-wsl2-systemd-script/issues/36#issuecomment-732090101 by editing the related file with...

Ubuntu 22.04 LTS nsenter: cannot open /proc/xxx/ns/time: No such file or directory

> @CleanHit: sure, that systemd is running? > > `ps aux | grep systemd` Here is my output of `ps aux | grep systemd`, I've replaced my non-root username with...

Ubuntu 22.04 LTS nsenter: cannot open /proc/xxx/ns/time: No such file or directory

@apos thanks for the informative post. I didn't mention that I was using the winsows terminal app, as I didn't think that it makes any difference. I gues it did...