View Issue Details

IDProjectCategoryView StatusLast Update
0005606Kali LinuxKali Package Bugpublic2019-08-15 13:32
Reportermaverick Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Product Version2018.4 
Summary0005606: Metasploit Database Setup in Kali Docker Container
Description

Hello,

This issue is happening with the official docker image at the official docker repository
https://hub.docker.com/r/kalilinux/kali-linux-docker

When I try to start the msf database I get the following error:

root@kali:/# service postgresql start
[ ok ] Starting PostgreSQL 11 database server: main.
root@kali:/# msfdb init
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
[+] Starting database
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
[i] The database appears to be already configured, skipping initialization
root@kali:/#

I would like to know how to go around or fix this error.
Thanks.

Steps To Reproduce

Use msfdb init on the docker image.

Activities

crash

crash

2019-08-07 15:22

reporter   ~0010819

Hi!
I made some tests here, you can ignore this error.
As far as I have tested, everything is working fine.

To double-check it, you can connect in the database and verify the existence of the following databases:
msf
msf_test

rhertzog

rhertzog

2019-08-15 13:32

administrator   ~0010874

Those errors are only a sign that systemd is not running in the container. They might be harmless, I haven't checked. We could improve the script to detect the lack of systemd and switch to manual startup of services but that script is likely to replaced by the upstream version (cf 0005262) so I don't think we should care about this at this point.

Issue History

Date Modified Username Field Change
2019-07-30 11:48 maverick New Issue
2019-08-07 15:22 crash Note Added: 0010819
2019-08-15 13:32 rhertzog Assigned To => rhertzog
2019-08-15 13:32 rhertzog Status new => closed
2019-08-15 13:32 rhertzog Resolution open => won't fix
2019-08-15 13:32 rhertzog Note Added: 0010874