-
Notifications
You must be signed in to change notification settings - Fork 824
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
WSL 18.04 apt upgrade failure #3274
Comments
https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1774120 Ubuntu are taking action by changing the package management script. |
@therealkenc Do we have an exact fix for this issue? or do we have to wait for next Ubuntu release? |
@macxfadz A temporary workaround is here: #1761 (comment) |
Or maybe someone can confirm whether just purging the thing is a viable solution (I haven't looked). |
@therealkenc Preliminary testing shows that simply purging doesn't work, but it was worth a shot.
|
When the ebtables upgrade script invokes the ebtables stop init script ebtables tries to open a socket and fails. Either because ebtables is at fault for misinterpreting the socket response or because WSL hasn't fully implemented iptables (although it seem to suggest WSL should support the syscalls in question here), why it fails is not entirely clear. Either way it ends up throwing a permissions error and the upgrade script shuts the whole show down. It doesn't matter what you run as or what runlevel. The workaround linked above works. The patch coming to the init script similarly just ignores the error. The patch works well in Cosmic, should be backported to Bionic shortly. |
Well, anything I could say would be speaking for Balint, which I don't. All I think he is trying to say is that etables could deal better with the error returned by WSL, which makes etables technically more correct, and thus addresses the hard fail.
In the #1451 OP, |
I see. Thank you for clearing that up. |
@therealkenc @sirredbeard - guys any elegant fix for this issue please ? :| |
by holding/disabling |
@akshaybabloo sounds like we have to next release of WSL ? is n't it ? |
@macxfadz yep. Looks like that. Or even a patch would be enough |
ebtables is old software that few actually use any more. It is maintained as legacy software by the developers that inherited it who only provide the most basic security patches and updates. ebtables is also not compatible with WSL yet because the WSL layer hasn't fully implemented all the advanced networking calls that ebtables and it's parent software iptables uses. So no one is really using ebtables on WSL. This bug, in the upgrade script on Ubuntu 18.04, only affects Ubuntu 18.04 images. So Ubuntu 16.04, OpenSUSE, SEL, and Kali users are unaffected. The fix is for the upgrade script in Ubuntu 18.04 to ignore the error when ebtables tries something not yet supported by WSL as part of the upgrade process. The second post on this thread contains a link to the Ubuntu bug report. If you look you will see a patch in Ubuntu has been generated, pushed to Cosmic, which is 18.10 in progress, for testing, and will filter down to Bionic, 18.04, in due time. Windows or WSL itself will not need a patch, although it's possible eventually WSL will support the network calls ebtables is flunking out on during the upgrade. |
@sirredbeard Thanks for the info ...if we holding/disabling ebtables in ubuntu 18.04 if you don't mind , can you please tell me what are the side effects we can expect? and one thing though, why is it working with 16.04 fine? as you mentioned here
due to 18.04 upgrade script update? |
Very little actually relies on ebtables these days, it's just there for legacy support on some servers. Given that ebtables doesn't work on WSL at this time, holding ebtables upgrades in WSL will have no real effect. Holding it means it simply won't get any updates via apt-get -upgrade. WSL is rolling out support for iptables which it means it's possible ebtables could, by extension, be supported too, there's no real demand for it though. Ebtables is legacy software in maintenance mode, there are modern more secure tools for performing it's functionality. Ubuntu is even working on a layer to wrangle iptables. I imagine eventually upstream distros like Debian will deprecate ebtables in time.
The issue occurs when the ebtables upgrade script calls ebtables to stop it and ebtables fails. The issue only occurs when ebtables is upgraded via apt. It is working fine in 16.04 because 16.04 does not ever upgrade ebtables, there's really no need to. ebtables itself won't work on 16.04, SLES, Kali, or Debian either. |
Thanks @sirredbeard can confirm that the patch has been pushed for 18.10. |
@sirredbeard Thank you for the explanation really helpful. |
@sirredbeard как вариант удалить после установочный скрипт
ls /var/lib/dpkg/info/qemu-user-static*
|
This solved the issue temporarily I guess. 💃 |
@Hypnoes but mine fix for the time... that's why I mentioned "temporarily" ...sorry |
Interesting. Updated ebtables today (via aptitude ui) and it didn't error out. |
@tralston Couldn't get you, can you mentioned what do you mean by "aptitude ui"? and what modification have you carried out in order to error wipe away? |
@macxfadz |
The ebtables problem has been fixed. No need to hold the package anymore on Ubuntu 18.04.
|
Good to know. Closing external. [Contrast #767 and friends.] |
I recently downloaded Ubuntu 18.04 App from Microsoft App Store.
Subsequently, I update app packages through
sudo apt-get update
and then,sudo apt-get upgrade
then I the following message came up with errors (just fresh WSL system nothing has been installed),
and, there are after I installed GCC, clang, gdb, and python3 also it's getting same upgrading error saying -
Please help me to resolve this issue.
Thank you.
The text was updated successfully, but these errors were encountered: