[windscribe-cli] can't install in Docker container

[airdrummingfool]

Describe the bug
I am trying to install windscribe-cli in Docker, but I get a few errors and the installation fails.

Errors:

• System has not been booted with systemd as init system (PID 1). Can't operate.
• Failed to connect to bus: Host is down

Relevant log:

 > [4/4] RUN apt install ./windscribe.deb:                                                                                         
0.214                                                                                                                              
0.214 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.                                              
0.214                                                                                                                              
0.217 Reading package lists...                                                                                                     
0.230 Building dependency tree...
0.231 Reading state information...
0.243 The following NEW packages will be installed:
0.243   windscribe-cli
0.429 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
0.429 Need to get 0 B/21.4 MB of archives.
0.429 After this operation, 0 B of additional disk space will be used.
0.429 Get:1 /windscribe.deb windscribe-cli amd64 2.13.4 [21.4 MB]
0.536 debconf: delaying package configuration, since apt-utils is not installed
0.577 Selecting previously unselected package windscribe-cli.
(Reading database ... 7888 files and directories currently installed.)
0.585 Preparing to unpack /windscribe.deb ...
0.607 /var/lib/dpkg/tmp.ci/preinst: line 19: killall: command not found
0.609 System has not been booted with systemd as init system (PID 1). Can't operate.
0.609 Failed to connect to bus: Host is down
0.609 Finish pre-install script
0.610 Unpacking windscribe-cli (2.13.4) ...
2.482 Setting up windscribe-cli (2.13.4) ...
2.508 Created symlink /etc/systemd/system/multi-user.target.wants/windscribe-helper.service → /lib/systemd/system/windscribe-helper.service.
2.515 System has not been booted with systemd as init system (PID 1). Can't operate.
2.515 Failed to connect to bus: Host is down
2.516 dpkg: error processing package windscribe-cli (--configure):
2.516  installed windscribe-cli package post-installation script subprocess returned error exit status 1
2.529 Errors were encountered while processing:
2.529  windscribe-cli
2.537 E: Sub-process /usr/bin/dpkg returned an error code (1)

OS and app information:

• OS: Ubuntu 22.04 in Docker
• App version 2.13.4-alpha (I also tried the latest stable version, 2.12.7)

To Reproduce
docker buildx build windscribe --file=windscribe/windscribe.dockerfile

Dockerfile (in windscribe/windscribe.dockerfile):

FROM ubuntu:22.04

# Set environment variables
ENV DEBIAN_FRONTEND=noninteractive \
    TZ=UTC

# Install dependencies
RUN apt -y update && \
    apt -y dist-upgrade && \
    apt -y install curl iptables libglib2.0-0 libdbus-1-3 sudo net-tools policykit-1 iproute2 iputils-ping iw ethtool && \
    apt -y autoremove && apt -y clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

# Download Windscribe
# RUN curl --location https://github.com/Windscribe/Desktop-App/releases/download/v2.12.7/windscribe-cli_2.12.7_amd64.deb -o windscribe.deb
RUN curl --location https://github.com/Windscribe/Desktop-App/releases/download/v2.13.4/windscribe-cli_2.13.4_guinea_pig_amd64.deb -o windscribe.deb

# Install Windscribe
RUN apt install ./windscribe.deb

Expected behavior
Windscribe is successfully installed in a Docker container.

Additional context
This might be more of a feature request than a bug report.

Thanks for making such a great VPN!

[jaxu]

May I ask what the use case is for this? Even had this worked, and you could connect, the VPN would not affect anything outside the container.

[hridoy14h]

#204 (comment)

[airdrummingfool]

Certainly! Using Docker Compose, one container's network stack can be shared with another container using the syntax network_mode: service:[host service]. It's not documented very well, but here are a couple relevant discussions about it.

I've been using that setup for a long time with this container and it has worked great. Unfortunately a few weeks ago the container started failing to connect to Windscribe, and I haven't been able to figure out why. It is built using the legacy Windscribe CLI (version 1.4) so I wanted to see if perhaps that was the reason.

[jaxu]

Thanks, we'll look into it.