debootstrap | Bootstrap a basic Debian system

In case somebody is facing the same problem. I solved it using Docker container with separate SSH server and all required software installed on it.

It could be due to issues occurred when a windows update and docker image not updated accordingly. Try rolling back to a previous version can fix it.

Further, try experimenting with different docker images like

This kind of "unable to mount root fs on unknown-block" error has several possible causes:

• You asked the kernel to use the wrong device as the rootfs (or you didn't specify, and the built-in default is the wrong one)
• You asked the kernel to use the right device as the rootfs, but the kernel doesn't have a device driver for it compiled in. (This might include more complicated cases like "the device is a PCI device and the kernel doesn't have the PCI controller driver compiled in.")
• You asked the kernel to use the right device as the rootfs, and the kernel does have a driver for it, but it couldn't find the hardware, perhaps because the QEMU command line is incorrect

An important clue in figuring out which is the problem is to look at the part of the kernel log just before the "Kernel panic" part of the log. The kernel should print a list of "available partitions", which are the devices that it has a driver for and which are present. If that list contains a plausible looking device name, as in your case (where "vda" is listed as provided by the "virtio_blk" driver) then you now know what the root device name should be, and all you need to do is fix the kernel command line, eg "root=vda". Note that this list is a list of available partitions, so if your disk image has multiple partitions they should show up in the list as "vda1", "vda2", etc. (In this case it looks like your image is a single filesystem, not a disk image with multiple partitions, so only "vda" is in the list.)

If the kernel's list of available partitions doesn't include anything that looks like the disk you were expecting, then either the kernel is missing the driver, or the QEMU command line doesn't have the option to provide the device. This is a little harder to debug, but there may be useful information earlier in the kernel bootup log where the kernel probes for hardware -- for instance there should be logging when the PCI controller is probed. You can also of course double-check the config file for your kernel to see if the right CONFIG options are set.

If you're using a standard distro kernel then these usually have all the usual devices built-in, and your first check should be your QEMU command line. If you built your own kernel from source, check your config, especially if you were trying to achieve a "minimal" kernel with only the desired drivers present.

try this regex :

bash(1) isn’t all that “magic,” though it certainly makes its users feel like wizards! The key to deciphering it is to know which manpages to look at. Or, if you are a language person (like me), to realize that bash is one little glue language; a bunch of other little languages are sprinkled on top of it in the form of little tools like grep(1), sed(1), awk(1), cut(1), etc.

So, let’s dig in:

By default, the PATH used in the container is the PATH of the environment you run it from. An easy way to ensure the path is what you want is set: PATH=/path/to/strelka/bin:$PATH under %environment.

A simple definition file you can you to quickly play around with:

You must allow anybody to start X11:

OK, I think I figured it out.

It works when I select stretch as Debian version in debootstrap command.

If you're willing to modify the definition file and use a different bootstrap source, the following builds successfully on 18.04 LTS and should on 16.04 as well.