vboxweb in 5.2.18-dfsg-2~ubuntu18.04.3 ignores VBOXWEB_HOST ip in /etc/default/virtualbox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
PROBLEM:
Phpvirtualbox depends on having vboxweb starup and listening properly. I installed the virtualbox 5.2.18-
VBOXWEB_USER=vbox
VBOXWEB_
I finally understood that some combination of systemd unit file and vboxweb itself was ignoring the default in my /etc/default/
https:/
EXPECTED BEHAVIOR:
The repo package should source /etc/default/
ENVIRONMENT:
Description: Ubuntu 18.04.2 LTS
Release: 18.04
virtualbox 5.2.18-
The Ubuntu systemd unit script appears to be the same in virtualbox 6.0.4-dfsg-5 from disco.
ADDITIONAL INFORMATION:
On a whim I decided to install the official 6.0, then 5.2 packages from Oracle. Both picked up my environment variable changes flawlessly.
It looks like the way the Oracle package starts vboxweb(oracle) is quite different from the ubuntu package. Does this have something to do with why the changes aren't being picked up?
UBUNTU - /lib/systemd/
cat debian/
[Unit]
Description=
After=network.
[Service]
Type=forking
ExecStart=
PIDFile=
[Install]
WantedBy=
From:
https:/
https:/
ORACLE - /lib/systemd/
cat /lib/systemd/
[Unit]
SourcePath=
Description=
Before=
After=vboxdrv.
Conflicts=
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=
ExecStop=
[Install]
WantedBy=
NOTE: The systemd unit file uses this script: https:/
Bionic-proposed repository, now has Virtualbox 5.2.32 in there...
Can you confirm this fixes the above issue over the bionic 5.2.18 version?
If not, it may be possible (if hurry!) to get the community maintainer/updater to fix that issue in proposed update as well.