-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Out of the box Snap support #618
Comments
Thank you for your suggestion we are working on something. But for Fedora Remix, so now we know that Pengwin users would like to have it also |
@crramirez Thanks for the quick reply, do you have a rough timeline ? |
No more than the end of the year, probably in two months |
Hello, I recommend you to assist WSLConf. Will be a talk about snaps in WSL Regards |
Is it still in WIP? |
Hello @Peredery, Yes, we are still working on that but it will take more time to release a beta. Regards, |
Any update on this? |
Hello @kotx, Sadly no. But the fact that you ask for it, raises its priority. Regards, |
Hello @kotx @Hebilicious @Peredery The lastest version of Pengwin 22.11.4 includes an implementation of SystemD regardless you are in Windows 10 or 11. It can enabled via pengwin-setup |
I've tried installing snap using
I'm on
Could someone clarify how I could use this feature? :) |
Hello @flexchar Did you enabled systemd via pengwin-setup? Regards |
Yep, I've just done it. And tried reinstalling snap but I'm sitting on the same error. I can see it tried to create service but then it's not found. lukas in ~ λ sudo apt install snapd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
zenity | kdialog
The following NEW packages will be installed:
snapd
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 13.3 MB of archives.
After this operation, 56.5 MB of additional disk space will be used.
Get:1 https://deb.debian.org/debian bullseye/main amd64 snapd amd64 2.49-1+deb11u2 [13.3 MB]
Fetched 13.3 MB in 12s (1,155 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package snapd.
(Reading database ... 130377 files and directories currently installed.)
Preparing to unpack .../snapd_2.49-1+deb11u2_amd64.deb ...
Unpacking snapd (2.49-1+deb11u2) ...
Setting up snapd (2.49-1+deb11u2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/snapd.recovery-chooser-trigger.service → /lib/systemd/system/snapd.recovery-chooser-trigger.service.
Created symlink /etc/systemd/system/multi-user.target.wants/snapd.seeded.service → /lib/systemd/system/snapd.seeded.service.
Created symlink /etc/systemd/system/cloud-final.service.wants/snapd.seeded.service → /lib/systemd/system/snapd.seeded.service.
Unit /lib/systemd/system/snapd.seeded.service is added as a dependency to a non-existent unit cloud-final.service.
Created symlink /etc/systemd/system/multi-user.target.wants/snapd.service → /lib/systemd/system/snapd.service.
Created symlink /etc/systemd/system/sockets.target.wants/snapd.socket → /lib/systemd/system/snapd.socket.
Processing triggers for man-db (2.10.1-1~bpo11+1) ...
Processing triggers for dbus (1.12.24-0+deb11u1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
lukas in ~ λ service snap status
snap: unrecognized service
lukas in ~ λ service snapd status
snapd: unrecognized service
lukas in ~ λ service --status-all
[ - ] apparmor
[ - ] dbus
[ ? ] hwclock.sh
[ - ] procps
[ - ] rsync
[ - ] ssh
[ - ] sudo
[ + ] udev
[ - ] unattended-upgrades
[ - ] x11-common |
sudo systemctl enable --now snapd |
Somethung is completely wrong in your pengwin installation that the Interop is not running. Anyway, to enable systemd add
To your /etc/wsl.conf file then And try again to start snapd |
Damn, given your support, you should totally charge more for this distro. I appreciate it!! That being said, still not going through. I've also shut off docker in case it was messing up and ran > sudo systemctl enable --now snapd
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down Meanwhile, to be respectful of your time, perhaps I should just dedicate time to wipe it all and do a fresh install. ;) |
You are very welcome! :-D Considering the WSL version you sent, the systemd should already be working. I you haven't wiped it all, could you please send me the content of your Also, the content of |
Absolutely! lukas in ~ λ cat $HOME/winhome/.wslconfig
[wsl2]
memory=25GB
swap=0
localhostForwarding=true
[boot]
systemd=true lukas in ~ λ cat /etc/wsl.conf
[automount]
enabled = true
options = "metadata,uid=1000,gid=1000,umask=0022,fmask=11,case=off"
mountFsTab = true
crossDistro = true
[network]
generateHosts = true
generateResolvConf = true
[filesystem]
umask = 0022
[user]
default=lukas |
Ok remove
from I still don't see signals why pengwin-setup thinks that you are in WSL1. Could you please |
It was the same. But since my vs code began hanging I decided to restart PC. It happens couple times a month. And after a reboot it worked. So it may have had worked all along if I've tried restarting it haha. Oh, and I'll share all env variables with you: lukas in ~ λ env | grep WSL
WSL2_GUI_APPS_ENABLED=1
WSLENV=WT_SESSION::WT_PROFILE_ID
WSL_INTEROP=/run/WSL/269_interop
WSL_DISTRO_NAME=WLinux
WSL_HOST_IP=172.19.224.1 |
Is your feature request related to a problem? Please describe.
snap requires systemctl wich isn't working yet in wsl (wsl issue here).
Describe the solution you'd like
A more wsl-y solution will hopefully be provided my the wsl team soon. In the meantime it would be nice to have a workaround implemented in Pengwin.
Describe alternatives you've considered
There's some workarounds, check the WSL issues. An out of the box solution would be ideal.
Additional context
//
The text was updated successfully, but these errors were encountered: