Error when installing on Ubuntu 22.04 in WSL windows

Virtualmin
1
SYSTEM INFORMATION
OS type and version Ubuntu 22.04
Webmin version 2.105
Virtualmin version 7.3.4
Related packages SUGGESTED

When trying to install Virtualmin with the command
sudo sh -c “$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)” – --bundle LEMP
I get an error when installing on point 3 of 4.
I tried to find an error on the forum, I only found that port 10000 was busy during installation.
I checked it myself with sudo lsof -nP -i:10000
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
miniserv. 35856 root 5u IPv4 454418 0t0 TCP *:10000 (LISTEN)
miniserv. 35856 root 6u IPv4 454419 0t0 UDP *:10000
Tried to kill these processes, but they restart.

Could my error be related to this? I also tried to install on Ubuntu 20.04, there was also some kind of error, but a different one… On the forum they recommended using 22.04. Can you please tell me something, or should I try to install it on a real hosting, but it won’t work in WSL? If so, why?

▣▣▣◻ Phase 3 of 4: Installation
Checking and installing system package updates :heavy_check_mark:
Installing Virtualmin 7 and all related packages [ERROR] Failed with error: 100
✘

[ERROR] Something went wrong. Exiting.
[ERROR] The last few log entries were:
Processing triggers for sgml-base (1.30) …
Setting up python3-docutils (0.17.1+dfsg-2) …
Setting up awscli (1.22.34-1) …
Processing triggers for php8.1-cli (8.1.2-1ubuntu2.15) …
Processing triggers for php8.1-cgi (8.1.2-1ubuntu2.15) …
Processing triggers for dovecot-core (1:2.3.16+dfsg1-3ubuntu2.2) …
Processing triggers for php8.1-fpm (8.1.2-1ubuntu2.15) …
Errors were encountered while processing:
postfix
postfix-pcre
virtualmin-lemp-stack-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)
Installing Virtualmin 7 and all related packages: [2024-04-15 23:34:20 +04] [ERROR] Failed with error: 100
[2024-04-15 23:34:20 +04] [ERROR] Something went wrong. Exiting.
[2024-04-15 23:34:20 +04] [ERROR] The last few log entries were:

I also tried to google it on the Internet, after the command
sudo dpkg --configure -a
Postfix configuration begins. I go through it and then see it in ssh

Postfix (main.cf) is now set up with the changes above. If you need to make
changes, edit /etc/postfix/main.cf (and others) as needed. To view Postfix
configuration values, see postconf(1).

After modifying main.cf, be sure to run ‘systemctl reload postfix’.

Running new aliases
newaliases: fatal: bad string length 0 < 1: mydomain =
dpkg: error processing package postfix (–configure):
installed postfix package post-installation script subprocess returned error exit status 75
dpkg: dependency problems prevent configuration of postfix-pcre:
postfix-pcre depends on postfix (= 3.6.4-1ubuntu1.3); however:
Package postfix is not configured yet.

dpkg: error processing package postfix-pcre (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of virtualmin-lemp-stack-minimal:
virtualmin-lemp-stack-minimal depends on postfix; however:
Package postfix is not configured yet.
virtualmin-lemp-stack-minimal depends on postfix-pcre; however:
Package postfix-pcre is not configured yet.

dpkg: error processing package virtualmin-lemp-stack-minimal (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
postfix
postfix-pcre
virtualmin-lemp-stack-minimal

Could it be that there is no “domain” or WSL hostname?

2

It turned out that the problem was really in the hostname.
By default, my name comes from Windows. LAPTOP-MBIU0LQL
Afterwards I replaced
sudo hostname test.webmin.com
And during the installation, for some reason he indicated to me that the hostname was not correct, I once again confirmed that it was test.webmin.com and everything worked out!
It seems to me that the hostname check needs to be improved. Because she didn’t work on the name that was causing problems, and when everything was ok, on the contrary, she asked again.

1 Like
3

WSL is a issue, not sure things will work.

4

I would be very surprised if everything works in WSL. It’s an impressive piece of engineering, and I like having it when I have to use a Windows system for work, but I would not try to run a virtual hosting stack on it.

I’m reasonably confident you’re going to have more problems down the road.

5

As an aside, I thought I read that Microsoft will be discontinuing WSL in the future… anyone else here that?

6

I doubt Microsoft will discontinued WSL, only in the sense they will bring out WSL2 and WSL3 etc…

This technology allows them a much larger client base.

7

Going off topic.

1 Like
8

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.