arkane-systems / bottle-imp Goto Github PK

View Code? Open in Web Editor NEW

104.0 104.0 4.0 171 KB

A spinoff of genie to supplement WSL's new built-in systemd support.

License: Other

Shell 4.63% Makefile 15.72% C 2.04% Python 67.15% Roff 10.46%

bottle-imp's People

Contributors

Stargazers

Watchers

Forkers

scaryrawr dbbao sitsaz omegaice

bottle-imp's Issues

windows app paths missing from $PATH

Hi,
Thank you for bottle-imp. 🙏

When using bottle-imp, I have a small issue with my PATH.

Inside a session started with imp -s my PATH envvar is missing the "windows apps paths" (eg: /mnt/c/windows/system32 etc.).

When I run a session without imp, my PATH envvar contains the paths.

The symptoms are code . and explorer.exe crashing with "command not found" for exemple.

I'm using an Ubuntu 22.04 WSL2 instance.

My current work-around is to start a imp session aside and then work inside a "normal" WSL session.

no DISPLAY environment variable specified

when i try to run firefox i get this error. trying to set the variable manually won't do anything.
chromium will throw "missing x server or $display"
any ideas?

most of these errors happen with both regular systemd and bottle-imp
i've tried multiple solutions and none of them worked

binary imp -i fails w/ keyerror

running opensuse tumbleweed compiled binary directly on latest wsl2.

unsure what to do here-i don't know why there would be an IMP_LOGNAME present for initiation. Is this something set at package installation?

andrew@Andrew-Ryzen:~> sudo bottle-imp/binsrc/out/imp -i
Traceback (most recent call last):
  File "/usr/lib64/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib64/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/andrew/bottle-imp/binsrc/out/imp/__main__.py", line 197, in <module>
  File "/home/andrew/bottle-imp/binsrc/out/imp/__main__.py", line 166, in entrypoint
  File "/home/andrew/bottle-imp/binsrc/out/imp/helpers.py", line 12, in get_login_session_user
  File "/usr/lib64/python3.10/os.py", line 679, in __getitem__
    raise KeyError(key) from None

WSL instance keeps stopping despite imp initialized

Current /etc/wsl.conf config file (see the [boot] section):

[automount]
enabled = true
root = /mnt
options = "metadata,uid=1000,gid=1000,umask=077,fmask=11,case=off"
mountFsTab = true

[boot]
systemd = true
command = imp --initialize

[user]
default = jellium

[interop]
enabled = false
appendWindowsPath = false

After startup, ps aux|grep imp returns:

root         674  0.0  0.0   2576   900 ?        Ss   01:24   0:00 /bin/sh /usr/lib/bottle-imp/wait-forever.sh
jellium        978  0.0  0.0   6332  1988 pts/0    S+   01:25   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox imp

However, when closing all terminal windows of this WSL instance, wsl --list --verbose returns after ca. 15 seconds:

  NAME      STATE           VERSION
* Debian    Stopped         2

What am I missing?
Thank you.

bottle-imp cannot be installed on Debian bullseye because of libc6 version

I tried to install bottle-imp, but apt throws this error:

$ sudo apt install bottle-imp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bottle-imp : Depends: libc6 (>= 2.34) but 2.31-13+deb11u6 is to be installed
E: Unable to correct problems, you have held broken packages.

Would you mind rebuilding your package with libc6 2.31 for bullseye?

systemd-sysctl.service failed to load

Hello, today I start bottle-imp, and got this:

❯ imp -i
imp: WARNING: systemd is in degraded state, issues may occur!
imp: check for failed units with "systemctl --failed".
imp: systemd environment initialized and instance holding
❯ systemctl --failed
  UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
● systemd-sysctl.service loaded failed failed Apply Kernel Variables

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
❯ sudo systemctl status systemd-sysctl
× systemd-sysctl.service - Apply Kernel Variables
     Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
     Active: failed (Result: exit-code) since Tue 2022-11-15 22:14:13 CST; 17s ago
       Docs: man:systemd-sysctl.service(8)
             man:sysctl.d(5)
    Process: 38 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=243/CREDENTIALS)
   Main PID: 38 (code=exited, status=243/CREDENTIALS)

Need help to find where the problem is. Thank you!

Distro: Archlinux

WSL 版本： 0.70.5.0
内核版本： 5.15.68.1
WSLg 版本： 1.0.45
MSRDC 版本： 1.2.3575
Direct3D 版本： 1.606.4
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows版本： 10.0.25236.1010

BTW, I manually update wsl to 0.70.8 and found wslg do not work properly, then I downgrade it to 0.70.5. I'm not sure if it cause the problem.

`imp: WARNING: systemd is in degraded state, issues may occur!`

First of all, thank you very much for putting a lot of work to support systemd in WSL.

I just tried 0.4 in ArchWSL. Installed using sudo pacman -U and then updating my WSL launch command to wsl imp -s.

Everytime I launched new shell ("tab"/profile in Windows Terminal), I got this error message.

imp: WARNING: systemd is in degraded state, issues may occur!

Running systemctl status will output this.

❯ systemctl status
Failed to dump process list for '8atagor', ignoring: Input/output error
● 8atagor
    State: degraded
    Units: 255 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 1 units
    Since: Sun 2022-09-25 20:18:31 +07; 12min ago
  systemd: 251.4-1-arch
  Tainted: cgroupsv1
   CGroup: /

However, running systemctl --user status will output this instead.

❯ systemctl --user status
● 8atagor
    State: running
    Units: 149 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Sun 2022-09-25 20:18:32 +07; 13min ago
  systemd: 251.4-1-arch
  Tainted: cgroupsv1
   CGroup: /user.slice/user-1000.slice/[email protected]
           ├─app.slice
           │ ├─at-spi-dbus-bus.service
           │ │ ├─965 /usr/lib/at-spi-bus-launcher
           │ │ ├─971 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus
           │ │ └─978 /usr/lib/at-spi2-registryd --use-gnome-session
           │ └─emacs.service
           │   └─849 /usr/bin/emacs --daemon
           ├─init.scope
           │ ├─95 /usr/lib/systemd/systemd --user
           │ └─96 "(sd-pam)"
           └─session.slice
             └─dbus.service
               └─962 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

I tried with emacs unit (as shown above) and yes it works flawlessly (before this, emacs daemon will crash every time I open emacsclient GUI. TUI no issue tho, but this is not imp issue).'

It might helps you debug a bit. Thank you again.

System info:

WSL version: 0.67.6.0
Kernel version: 5.15.62.1
WSLg version: 1.0.44
MSRDC version: 1.2.3401
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.521

WSL distro: ArchWSL
systemd 251 (251.4-1-arch)

`code-insiders` command no longer works after installing

Works before but after installing the command is not found anymore.

`[email protected]` failed when `bottle-imp` is installed

Hello !

Since the 1.1.7 version of the WSL2, I encounter an issue with bottle-imp is installed (used or not).

The problem is related to - I guess - systemd-logind not finding the user folder under /run/user/<uid> on WSL2 start with systemd mode and therefore the user service [email protected] failed to start :

Apr 13 17:42:14 buran systemd[1]: Starting User Manager for UID 1000...
Apr 13 17:42:14 buran (systemd)[120]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Apr 13 17:42:14 buran (systemd)[120]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[f-bn] ruser=[<unknown>] rhost=[<unknown>]
Apr 13 17:42:14 buran (systemd)[120]: pam_unix(systemd-user:session): session opened for user f-bn(uid=1000) by (uid=0)
Apr 13 17:42:14 buran (systemd)[120]: pam_systemd(systemd-user:session): Failed to stat() runtime directory '/run/user/1000': No such file or directory
Apr 13 17:42:14 buran (systemd)[120]: pam_systemd(systemd-user:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
Apr 13 17:42:14 buran systemd[120]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
Apr 13 17:42:14 buran systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE

Indeed, the folder is empty :

f-bn@buran ~ $ ls -lsha /run/user
total 0
0 drwxr-xr-x  2 root root  40 Apr 13 17:42 .
0 drwxr-xr-x 19 root root 460 Apr 13 17:42 ..

I tried to look deeper and I can't find an explanation why this is failing when bottle-imp is installed (even when not used). Once I remove the package, the problem disappear like magic.... I have this issue even when creating a fresh instance of WSL2 from scratch and the issue is present even using ArchLinux or official Ubuntu 22.04/22.10 distributions.

Once bottle-imp package is removed and the WSL2 is restarted, this works fine :

f-bn@buran ~ $ ls -lsha /run/user
total 0
0 drwxr-xr-x  3 root root  60 Apr 13 17:50 .
0 drwxr-xr-x 18 root root 440 Apr 13 17:50 ..
0 drwx------  5 f-bn f-bn 120 Apr 13 17:50 1000
f-bn@buran ~ $ systemctl is-active [email protected]
active
f-bn@buran ~ $ journalctl -u [email protected]
Apr 13 17:50:11 buran systemd[1]: Starting User Manager for UID 1000...
Apr 13 17:50:11 buran (systemd)[110]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Apr 13 17:50:11 buran (systemd)[110]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[f-bn] ruser=[<unknown>] rhost=[<unknown>]
Apr 13 17:50:11 buran (systemd)[110]: pam_unix(systemd-user:session): session opened for user f-bn(uid=1000) by (uid=0)
Apr 13 17:50:11 buran systemd[110]: Queued start job for default target Main User Target.
Apr 13 17:50:11 buran systemd[110]: Created slice User Application Slice.
Apr 13 17:50:11 buran systemd[110]: Reached target Paths.
Apr 13 17:50:11 buran systemd[110]: Reached target Timers.

I was previously using the 1.1.3 version of WSL2 and I hadn't any problem of this kind, so I guess this seems related to some changes regarding /run/user since 1.1.7 version.

Here my WSL components version :

WSL version: 1.2.1.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1555

Kind regards

Smile, you are in AUR!

I made a hacky bash script to automatically fetch the PKGBUILD from the repo and update the AUR package. I have it running on a cronjob every 6 hours.

If you ever update bottle-imp, the AUR package updates automagically!

#!/bin/bash

wget -O PKGBUILD.new "https://raw.githubusercontent.com/arkane-systems/bottle-imp/master/PKGBUILD" 2>/dev/null
diff -q PKGBUILD PKGBUILD.new > /dev/null
if [[ $? == 0 ]]; then
	echo "No updates"
	rm PKGBUILD.new 
else
	echo "New pkgver, updating and commiting"
	mv PKGBUILD{.new,}
	export $(grep -m 1 pkgver PKGBUILD)
	makepkg --printsrcinfo > .SRCINFO
	git add PKGBUILD .SRCINFO
	git commit -m "Updating PKGBUILD to ${pkgver}"
	git push
fi

New update breaks `imp -s` on Ubuntu 22.04

Update to new bottle-imp version, and run imp -s. bottle-imp was the only updated package since WSL was last working.

While waiting for a patch is there any way to revert the update? I noticed that previous releases are replaced with new release when running apt update.

Failed to connect bus

bottle-imp ver 0.8. WSL 0.67.6.0.

❯ systemctl --user status
Failed to connect to bus: No such file or directory

cannot launch shell; systemd-machined is not active

First of all thanks for this! Have been using genie for ages.

I am using ArchWSL and have installed imp with the Makefile.

After running imp -i and shutting down WSL, I attempted to create a new session with wsl imp -s but it gives the error:

imp: cannot launch shell; systemd-machined is not active

I am able to start this service manually and then imp works, but it appears it can't be enabled as a service:

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Because of that, when WSL is shutdown and starts back up, the same error happens.

Any ideas? I am wondering if there's some kind of difference in behaviour between Debian and Arch.

`[email protected]` failed

This error only happens after WSL has been running for a while, when I restart WSL everything works fine. Might have something to do with running WSL from admin terminal.

imp: WARNING: systemd is in degraded state, issues may occur!
❯ systemctl --failed
  UNIT           LOAD   ACTIVE SUB    DESCRIPTION
● [email protected] loaded failed failed User Manager for UID 0

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
❯ systemctl status [email protected]
× [email protected] - User Manager for UID 0
     Loaded: loaded (/lib/systemd/system/[email protected]; static)
    Drop-In: /usr/lib/systemd/system/[email protected]
             └─timeout.conf
     Active: failed (Result: exit-code) since Sat 2022-10-15 10:21:29 EDT; 25min ago
       Docs: man:[email protected](5)
    Process: 795 ExecStart=/lib/systemd/systemd --user (code=exited, status=1/FAILURE)
   Main PID: 795 (code=exited, status=1/FAILURE)

Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[1]: Starting User Manager for UID 0...
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[795]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (u>
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[795]: pam_systemd(systemd-user:session): Runtime directory '/run/user/0' is not>
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[795]: pam_systemd(systemd-user:session): Not setting $XDG_RUNTIME_DIR, as the d>
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[795]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[1]: [email protected]: Failed with result 'exit-code'.
Oct 15 10:21:29 DESKTOP-RVHOL00 systemd[1]: Failed to start User Manager for UID 0.
lines 1-17/17 (END)

WSL info:

WSL version: 0.70.0.0
Kernel version: 5.15.68.1
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.674

imp v1.0 cannot install on arch

loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) bottle-imp-1.0-1

Total Installed Size:  0.04 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                               [################################] 100%
(1/1) checking package integrity                             [################################] 100%
(1/1) loading package files                                  [################################] 100%
(1/1) checking for file conflicts                            [################################] 100%
error: failed to commit transaction (conflicting files)
bottle-imp: /lib exists in filesystem (owned by filesystem)
Errors occurred, no packages were upgraded.

/lib is a symlink to /usr/lib/ in archlinux, package file should go to /usr/lib, or pacman will refuse to install.

`imp -i` fails when running in WSL

❯ imp -i
Traceback (most recent call last):
  File "/home/xenfo/.asdf/installs/python/3.10.8/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/xenfo/.asdf/installs/python/3.10.8/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/usr/lib/bottle-imp/imp/__main__.py", line 10, in <module>
  File "/usr/lib/bottle-imp/imp/helpers.py", line 6, in <module>
ModuleNotFoundError: No module named 'psutil'

WSL info:

WSL version: 0.70.0.0
Kernel version: 5.15.68.1
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.674

Note: wsl -e imp -i works fine

`bottle-imp` auto-generated units failed to be executed by `systemd`

I have updated to 1.0 however I still have several failed units.

❯ systemctl --failed
  UNIT                               LOAD   ACTIVE SUB    DESCRIPTION
● systemd-sysctl.service             loaded failed failed Apply Kernel Variables
● systemd-tmpfiles-clean.service     loaded failed failed Cleanup of Temporary Directories
● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev
● systemd-tmpfiles-setup.service     loaded failed failed Create Volatile Files and Directories

❯ sudo systemctl --type=service --all | grep imp
  imp-fixshm.service                     loaded    inactive dead    bottle-imp - Fix the /dev/shm symlink to be a mount
  imp-pstorefs.service                   loaded    inactive dead    bottle-imp - Kernel Persistent Storage File System
  imp-remount-root-shared.service        loaded    inactive dead    bottle-imp - Remount Root Filesystem Shared
  imp-securityfs.service                 loaded    inactive dead    bottle-imp - Kernel Security File System
  imp-wslg-socket.service                loaded    inactive dead    bottle-imp - WSLg socket remount service

❯ systemctl status imp-fixshm
○ imp-fixshm.service - bottle-imp - Fix the /dev/shm symlink to be a mount
     Loaded: loaded (/run/systemd/generator/imp-fixshm.service; generated)
     Active: inactive (dead)

❯ sudo systemctl enable imp-fixshm
Failed to enable unit: Unit /run/systemd/generator/imp-fixshm.service is transient or generated.

Now the units will failed even after I tried to restart it. All units failed with same "protocol error".

❯ sudo systemctl restart systemd-sysctl
[sudo] password for mangkoran:
Job for systemd-sysctl.service failed because the control process exited with error code.
See "systemctl status systemd-sysctl.service" and "journalctl -xeu systemd-sysctl.service" for details.

~
❯ systemctl status systemd-sysctl.service
× systemd-sysctl.service - Apply Kernel Variables
     Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
     Active: failed (Result: exit-code) since Mon 2022-11-28 12:31:53 +07; 15s ago
       Docs: man:systemd-sysctl.service(8)
             man:sysctl.d(5)
    Process: 1545 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=243/CREDENTIALS)
   Main PID: 1545 (code=exited, status=243/CREDENTIALS)

Nov 28 12:31:53 8atagor systemd[1]: Starting Apply Kernel Variables...
Nov 28 12:31:53 8atagor systemd[1545]: systemd-sysctl.service: Failed to set up credentials: Protocol error
Nov 28 12:31:53 8atagor systemd[1545]: systemd-sysctl.service: Failed at step CREDENTIALS spawning /usr/lib/systemd/systemd-sysct>
Nov 28 12:31:53 8atagor systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=243/CREDENTIALS
Nov 28 12:31:53 8atagor systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
Nov 28 12:31:53 8atagor systemd[1]: Failed to start Apply Kernel Variables.

~
❯ findmnt
TARGET                          SOURCE        FSTYPE      OPTIONS
/                               /dev/sdc      ext4        rw,relatime,discard,errors=remount-ro,data=ordered
├─/mnt/wsl                      none          tmpfs       rw,relatime
├─/usr/lib/wsl/drivers          drivers       9p          ro,nosuid,nodev,noatime,dirsync,aname=drivers;fmask=222;dmask=222,mmap,a
├─/usr/lib/wsl/lib              none          overlay     rw,relatime,lowerdir=/gpu_lib_packaged:/gpu_lib_inbox,upperdir=/gpu_lib/
├─/mnt/wslg                     none          tmpfs       rw,relatime
│ ├─/mnt/wslg/distro            /dev/sdc      ext4        ro,relatime,discard,errors=remount-ro,data=ordered
│ ├─/mnt/wslg/versions.txt      none[/etc/versions.txt]
│ │                                           overlay     rw,relatime,lowerdir=/systemvhd,upperdir=/system/rw/upper,workdir=/syste
│ └─/mnt/wslg/doc               none[/usr/share/doc]
│                                             overlay     rw,relatime,lowerdir=/systemvhd,upperdir=/system/rw/upper,workdir=/syste
├─/init                         rootfs[/init] rootfs      rw,size=2002932k,nr_inodes=500733
├─/dev                          none          devtmpfs    rw,nosuid,relatime,size=2002960k,nr_inodes=500740,mode=755
│ ├─/dev/pts                    devpts        devpts      rw,nosuid,noexec,noatime,gid=5,mode=620,ptmxmode=000
│ ├─/dev/hugepages              hugetlbfs     hugetlbfs   rw,relatime,pagesize=2M
│ └─/dev/mqueue                 mqueue        mqueue      rw,nosuid,nodev,noexec,relatime
├─/sys                          sysfs         sysfs       rw,nosuid,nodev,noexec,noatime
│ ├─/sys/fs/cgroup              tmpfs         tmpfs       ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755
│ │ ├─/sys/fs/cgroup/unified    cgroup2       cgroup2     rw,nosuid,nodev,noexec,relatime,nsdelegate
│ │ ├─/sys/fs/cgroup/cpuset     cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,cpuset
│ │ ├─/sys/fs/cgroup/cpu        cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,cpu
│ │ ├─/sys/fs/cgroup/cpuacct    cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,cpuacct
│ │ ├─/sys/fs/cgroup/blkio      cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,blkio
│ │ ├─/sys/fs/cgroup/memory     cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,memory
│ │ ├─/sys/fs/cgroup/devices    cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,devices
│ │ ├─/sys/fs/cgroup/freezer    cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,freezer
│ │ ├─/sys/fs/cgroup/net_cls    cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,net_cls
│ │ ├─/sys/fs/cgroup/perf_event cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,perf_event
│ │ ├─/sys/fs/cgroup/net_prio   cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,net_prio
│ │ ├─/sys/fs/cgroup/hugetlb    cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,hugetlb
│ │ ├─/sys/fs/cgroup/pids       cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,pids
│ │ ├─/sys/fs/cgroup/rdma       cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,rdma
│ │ ├─/sys/fs/cgroup/misc       cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,misc
│ │ └─/sys/fs/cgroup/systemd    cgroup        cgroup      rw,nosuid,nodev,noexec,relatime,xattr,name=systemd
│ ├─/sys/kernel/debug           debugfs       debugfs     rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/tracing         tracefs       tracefs     rw,nosuid,nodev,noexec,relatime
│ └─/sys/fs/fuse/connections    fusectl       fusectl     rw,nosuid,nodev,noexec,relatime
├─/proc                         proc          proc        rw,nosuid,nodev,noexec,noatime
│ └─/proc/sys/fs/binfmt_misc    binfmt_misc   binfmt_misc rw,relatime
├─/run                          none          tmpfs       rw,nosuid,nodev,mode=755
│ ├─/run/lock                   none          tmpfs       rw,nosuid,nodev,noexec,noatime
│ ├─/run/shm                    none          tmpfs       rw,nosuid,nodev,noatime
│ └─/run/user                   none          tmpfs       rw,nosuid,nodev,noexec,noatime,mode=755
│   └─/run/user/1000            none[/runtime-dir]
│                                             tmpfs       rw,relatime
├─/tmp/.X11-unix                none[/.X11-unix]
│                                             tmpfs       rw,relatime
├─/mnt/c                        drvfs         9p          rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;metadata;symli
├─/mnt/d                        drvfs         9p          rw,noatime,dirsync,aname=drvfs;path=D:\;uid=1000;gid=1000;metadata;symli
├─/mnt/e                        drvfs         9p          rw,noatime,dirsync,aname=drvfs;path=E:\;uid=1000;gid=1000;metadata;symli
├─/mnt/g                        drvfs         9p          rw,noatime,dirsync,aname=drvfs;path=G:\;uid=1000;gid=1000;metadata;symli
├─/mnt/h                        drvfs         9p          rw,noatime,dirsync,aname=drvfs;path=H:\;uid=1000;gid=1000;metadata;symli
├─/tmp                          tmpfs         tmpfs       rw,nosuid,nodev,nr_inodes=1048576
└─/var/lib/docker               /dev/sdc[/var/lib/docker]
                                              ext4        rw,relatime,discard,errors=remount-ro,data=ordered

~
❯ mount
none on /mnt/wsl type tmpfs (rw,relatime)
drivers on /usr/lib/wsl/drivers type 9p (ro,nosuid,nodev,noatime,dirsync,aname=drivers;fmask=222;dmask=222,mmap,access=client,msize=65536,trans=fd,rfd=7,wfd=7)
none on /usr/lib/wsl/lib type overlay (rw,relatime,lowerdir=/gpu_lib_packaged:/gpu_lib_inbox,upperdir=/gpu_lib/rw/upper,workdir=/gpu_lib/rw/work)
/dev/sdc on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
none on /mnt/wslg type tmpfs (rw,relatime)
/dev/sdc on /mnt/wslg/distro type ext4 (ro,relatime,discard,errors=remount-ro,data=ordered)
rootfs on /init type rootfs (rw,size=2002932k,nr_inodes=500733)
none on /dev type devtmpfs (rw,nosuid,relatime,size=2002960k,nr_inodes=500740,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620,ptmxmode=000)
none on /run type tmpfs (rw,nosuid,nodev,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime)
none on /run/shm type tmpfs (rw,nosuid,nodev,noatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
none on /mnt/wslg/versions.txt type overlay (rw,relatime,lowerdir=/systemvhd,upperdir=/system/rw/upper,workdir=/system/rw/work)
none on /mnt/wslg/doc type overlay (rw,relatime,lowerdir=/systemvhd,upperdir=/system/rw/upper,workdir=/system/rw/work)
none on /tmp/.X11-unix type tmpfs (rw,relatime)
drvfs on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;metadata;symlinkroot=/mnt/,mmap,access=client,msize=262144,trans=virtio)
drvfs on /mnt/d type 9p (rw,noatime,dirsync,aname=drvfs;path=D:\;uid=1000;gid=1000;metadata;symlinkroot=/mnt/,mmap,access=client,msize=262144,trans=virtio)
drvfs on /mnt/e type 9p (rw,noatime,dirsync,aname=drvfs;path=E:\;uid=1000;gid=1000;metadata;symlinkroot=/mnt/,mmap,access=client,msize=262144,trans=virtio)
drvfs on /mnt/g type 9p (rw,noatime,dirsync,aname=drvfs;path=G:\;uid=1000;gid=1000;metadata;symlinkroot=/mnt/,mmap,access=client,msize=262144,trans=virtio)
drvfs on /mnt/h type 9p (rw,noatime,dirsync,aname=drvfs;path=H:\;uid=1000;gid=1000;metadata;symlinkroot=/mnt/,mmap,access=client,msize=262144,trans=virtio)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
/dev/sdc on /var/lib/docker type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
none on /run/user/1000 type tmpfs (rw,relatime)

WSL version: 1.0.0.0
Kernel version: 5.15.74.2
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.819
---
Distro: ArchWSL
bottle-imp 1.0-1

`imp -l` no color

When I run imp -l my terminal loses color capability.
What can I do to get colors?