alexssd7 / linsk Goto Github PK

Potentially related to #1 - I just found this project, and am attempting to use it on a new mac laptop.

However, I can't seem to successfully build the VM image:

• brew install qemu done and successful
• go install github.com/AlexSSD7/linsk@latest success
• linsk version shows Linsk v0.2.1 darwin/arm64 go1.21.5

But when I run linsk build I get this:

❯ linsk build --overwrite
time=2023-12-17T15:46:10.507+10:30 level=INFO msg="Building VM image" caller=storage tags=3.18.3-aarch64 overwriting=true dst=/Users/cosmotherly/.linsk/3.18.3-aarch64-linsk1.qcow2
time=2023-12-17T15:46:10.536+10:30 level=WARN msg="Using unrestricted VM networking" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-12-17T15:46:10.540+10:30 level=INFO msg="Booting the VM" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-12-17T15:46:19.555+10:30 level=INFO msg="The VM is up, setting it up" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-12-17T15:46:34.050+10:30 level=INFO msg="The VM is ready" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-12-17T15:46:34.089+10:30 level=INFO msg="VM OS installation in progress" caller=storage subcaller=imgbuilder
time=2023-12-17T15:46:39.412+10:30 level=ERROR msg="Failed to set up Alpine Linux" caller=storage subcaller=imgbuilder error="run setup cmd (log: 'udhcpc: started, v1.36.1\\nudhcpc: broadcasting discover\\nudhcpc: broadcasting select for 10.0.2.15, server 10.0.2.2\\nudhcpc: lease of 10.0.2.15 obtained from 10.0.2.2, lease time 86400\\nwget: bad address 'mirrors.alpinelinux.org'\\nWarning! No mirror found'): Process exited with status 1"
time=2023-12-17T15:46:39.412+10:30 level=WARN msg="Canceling the VM context" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-12-17T15:46:39.471+10:30 level=WARN msg="Sending poweroff command to the VM" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-12-17T15:46:39.479+10:30 level=INFO msg="Shutting the VM down safely" caller=storage subcaller=imgbuilder subcaller=vm

I've tried running it with --vm-debug as it suggests, but a qemu window appears with a (qemu) prompt and nothing else.

I can curl mirrors.alpinelinux.org without issue and open it in my browser, so not sure what the problem is here... 🤔 any tips or pointers?

I don't find it in https://search.nixos.org/packages

Thanks for the solution.

Hi

So i am attempting to use this awesome project to mount a LUKS partition on macOS
sudo ./linsk_darwin_arm64_v0.2.2 run -l dev:/dev/disk6s1

but I would like to switch to using a keyfile, can this be done with the run command?
also, I get permission denied while trying to modify files in the share, what uid/gid should the folder be (on the mounted filesystem)?

& also, is it possible to attach a shell to a running vm? (which is run by run command)

Edit:
Figured out the user is linsk uid=1000, gid=1000 and the --debug-shell option! but would still be interested if passing a keyfile is supported

i also just noticed memory usage climbs when transferring files to the share
this is likely qemu disk caching if I am right?

or your -h output might be displaying it as KiB instead of MiB
--vm-mem-alloc uint32 Specifies the VM memory allocation in KiB. (the default is 2048 in LUKS mode) (default 512)

Hello,
When I try to build this on my Windows machine I get the following error:

time=2023-09-04T17:14:15.769+02:00 level=INFO msg="The VM is ready" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-09-04T17:14:15.812+02:00 level=INFO msg="VM OS installation in progress" caller=storage subcaller=imgbuilder
time=2023-09-04T17:14:21.220+02:00 level=ERROR msg="Failed to set up Alpine Linux" caller=storage subcaller=imgbuilder error="run setup cmd (log: 'udhcpc: started, v1.36.1\\nudhcpc: broadcasting discover\\nudhcpc: broadcasting select for 10.0.2.15, server 10.0.2.2\\nudhcpc: lease of 10.0.2.15 obtained from 10.0.2.2, lease time 86400\\nwget: bad address 'mirrors.alpinelinux.org'\\nWarning! No mirror found'): Process exited with status 1"
time=2023-09-04T17:14:21.221+02:00 level=WARN msg="Canceling the VM context" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-09-04T17:14:21.295+02:00 level=WARN msg="Sending poweroff command to the VM" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-09-04T17:14:21.303+02:00 level=INFO msg="Shutting the VM down safely" caller=storage subcaller=imgbuilder subcaller=vm

Best regards,
Maciej Błędkowski

Hi there,

I just ran linsk for the first time and I am getting this error on my MacBook Pro

Here are my Machine's details:

Model Name:	MacBook Pro
  Model Identifier:	MacBookPro16,1
  Processor Name:	8-Core Intel Core i9
  Processor Speed:	2,4 GHz
  Number of Processors:	1
  Total Number of Cores:	8
  L2 Cache (per Core):	256 KB
  L3 Cache:	16 MB
  Hyper-Threading Technology:	Enabled
  Memory:	64 GB
  System Firmware Version:	1916.40.8.0.0 (iBridge: 20.16.420.0.0,0)
  OS Loader Version:	564.40.4~27

And this is my terminal output:

./linsk_darwin_amd64_v0.2.0 build --vm-debug --overwrite                                                                                                                                                                                   
time=2023-10-12T15:55:44.851-07:00 level=INFO msg="Building VM image" caller=storage tags=3.18.3-x86_64 overwriting=true dst=/Users/admin/.linsk/3.18.3-x86_64-linsk1.qcow2
time=2023-10-12T15:55:49.867-07:00 level=WARN msg="Using unrestricted VM networking" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-10-12T15:55:49.872-07:00 level=INFO msg="Booting the VM" caller=storage subcaller=imgbuilder subcaller=vm
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
time=2023-10-12T15:55:57.881-07:00 level=INFO msg="The VM is up, setting it up" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-10-12T15:56:03.948-07:00 level=INFO msg="The VM is ready" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-10-12T15:56:08.949-07:00 level=ERROR msg="Failed to dial VM SSH" caller=storage subcaller=imgbuilder error="dial tcp: lookup localhost: i/o timeout"
time=2023-10-12T15:56:08.949-07:00 level=WARN msg="Canceling the VM context" caller=storage subcaller=imgbuilder subcaller=vm
time=2023-10-12T15:56:13.950-07:00 level=WARN msg="Failed to dial VM SSH to do graceful shutdown" caller=storage subcaller=imgbuilder subcaller=vm error="dial tcp: lookup localhost: i/o timeout"
qemu-system-x86_64: terminating on signal 15 from pid 8713 (<unknown process>)

Not sure if this is a bug and it should be autoincrementing the port, but I'd like to mount two different partitions to copy files between them. On a second instance, I get

time=2024-03-03T09:44:03.010+01:00 level=WARN msg="Using raw block device passthrough. Please note that it's YOUR responsibility to ensure that no device is mounted in your OS and the VM at the same time. Otherwise, you run serious risks. No further warnings will be issued." caller=vm
time=2024-03-03T09:44:03.016+01:00 level=INFO msg="Booting the VM" caller=vm
time=2024-03-03T09:44:03.034+01:00 level=WARN msg="Canceling the VM context" caller=vm
time=2024-03-03T09:44:03.034+01:00 level=ERROR msg="Failed to start the VM" error="cancel on exit: interrupt cmd: no such process (qemu stderr log: '[244 chars trimmed]wd=tcp:127.0.0.1:9004-:9004,hostfwd=tcp:127.0.0.1:9005-:9005,hostfwd=tcp:127.0.0.1:9006-:9006,hostfwd=tcp:127.0.0.1:9007-:9007,hostfwd=tcp:127.0.0.1:9008-:9008,hostfwd=tcp:127.0.0.1:9009-:9009: Could not set up host forwarding rule 'tcp:127.0.0.1:9000-:21'')"

Is there a configuration for the afp (or smb, ftp) port mapping to allow multiple mounts at once?

hi! i can't seem to mount my ext4 partition which is inside an lvm logical volume, itself inside a luks encrypted vg. the command 'linsk run -l dev:/dev/disk2s5 mapper/toaster-root ext4' starts running and prompts me for an encryption key but fails after that.

time=2023-09-25T14:56:18.688+01:00 level=INFO msg="Attempting to open a LUKS device" caller=file-manager vm-path=/dev/mapper/toaster-root
Enter Password:
time=2023-09-25T14:56:25.920+01:00 level=ERROR msg="Failed to mount the disk inside the VM" error="luks open: wait for cryptsetup luksopen cmd to finish (log: 'Device /dev/mapper/toaster-root does not exist or access denied.'): Process exited with status 4"
time=2023-09-25T14:56:25.920+01:00 level=WARN msg="Canceling the VM context" caller=vm
time=2023-09-25T14:56:25.967+01:00 level=WARN msg="Sending poweroff command to the VM" caller=vm

by using the shell, i can mount my disk without issue by first unlocking the /dev/vdb device with cryptsetup, scanning/activating the vgs, and mounting the lv.

i'm running macos (intel) and using qemu version 8.1.1, linsk version 0.1.1 maintenance release pre-built.

thanks:)

Hello. It's my first day using linsk, and I found a couple use cases that aren't covered in the documentation. I'd suggest listing them as examples, maybe in a separate file if you think the documentation is already explicit enough:

1. How to open a shell with a disk mapped (raw block device passthrough) for formatting? Answer: linsk shell dev:\\.\PhysicalDrive2
2. How to mount a luks partition (not a whole disk nor LVM): run -l dev:\\.\PHYSICALDRIVE2 vdb1

Also, is there a way to mount multiple disks in the same VM? I'd like to copy files and have the process be aware of Linux features like non-SMB filenames and hard links.

To clarify: I now realize that your LVM examples were intended to be the complete version of how to mount a partition, and they are also applicable to LUKS if followed carefully.

First and foremost, thanks again for putting together and publishing this tool.
This has most of my use cases covered, beside maybe some specific usage scenario.

Let us consider that I have a dual-booting system with Windows / MacOS and Linux.
On the Linux system, I have a LUKS encrypted partition with an ext4 FS that I would like to regularly access from the Windows system.

The physical drive is detected under windows as \\.\PhysicalDrive3, and the encrypted partition is detected as vdb1 by linsk.

As of now, after setting up linsk and running with linsk run -l dev:\\.\PhysicalDevice3 vdb1 ext4, it generates:
a. arbitrary IPv6 URL to connect via SMB Network Share
b. a username linsk, and
c. a random password.

For regular mounting of said LUKS partition, it would be desirable to have a fixed a. URL and c. password, so that the mounting process could be automated with a Batch script, for example.

This could be address by adding support for two flags, for example:

linsk run -l dev:\\.\PhysicalDevice3 vdb1 ext4 --share-address "MyFixedAddress" --share-password "MyFixedPassword"

Moreover, regarding --smb-address, it seems that it is tied to the address of the TAP device used to establish a virtual network between the QEMU VM and the host system. Even if it is not possible to set a human readable name, it would still be enough if the user can specify a dummy but fixed IPv6 address.
Also, not sure whether or not this is related to --share-listen.

Thanks a lot for your time.

Hi,
I'd like to access ext4 or lvm partitions from windows 11 on a laptop with i7-1360p processor using linsk.
VT-d is enabled in BIOS and I guess vt-x is permanently enabled( no enable/disable toggle in bios, lscpu shows vt-x in ubuntu ( dual boot ) ), hypervisor is also enabled.
I have tried to use linsk and get the following error as typing linsk shell:

C:\Users\cedri>linsk shell
time=2023-11-14T20:32:02.792+01:00 level=WARN msg="Using unrestricted VM networking" caller=vm
time=2023-11-14T20:32:02.816+01:00 level=INFO msg="Booting the VM" caller=vm
time=2023-11-14T20:32:02.994+01:00 level=WARN msg="Canceling the VM context" caller=vm
time=2023-11-14T20:32:03.165+01:00 level=ERROR msg="Failed to start the VM" error="wait for cmd to finish execution: context canceled; cancel: interrupt cmd: exit status 128 (qemu stderr log: 'qemu-system-x86_64.exe: unable to find CPU model 'host'')"

Any idea ?
Thanks !

Hello there.
Thanks a lot for making this tool and publishing it.
I have been looking for this kind of features for a while now, the WSL based alternative I found was not really cutting it.

Failing to mount LUKS device

Thought I would give it a try, but I stumbled upon this error I could not solve, so I was wondering if you had any idea on what might be the cause.

1. How it was installed
   Following INSTALL_WINDOWS.md:

• Grabbed the pre-built binaries from github, linsk v0.1.0 Initial release for amd64
• Installed QEMU and OpenVPN.

2. What I ran
   Following USAGE_WINDOWS.md, and running commands in cmd.exe started as administrator.

• building using linsk build
• Identified the device of interest: \\.\PhysicalDrive3
• Listing detected partitions using linsk ls returns:

linsk ls dev:\\.\PhysicalDrive3
time=2023-09-06T19:37:43.107+09:00 level=WARN msg="Using raw block device passthrough. Please note that it's YOUR responsibility to ensure that no device is mounted in your OS and the VM at the same time. Otherwise, you run serious risks. No further warnings will be issued." caller=vm
time=2023-09-06T19:37:43.156+09:00 level=INFO msg="Booting the VM" caller=vm
time=2023-09-06T19:37:58.318+09:00 level=INFO msg="The VM is up, setting it up" caller=vm
time=2023-09-06T19:38:05.043+09:00 level=INFO msg="The VM is ready" caller=vm
NAME     SIZE FSTYPE      LABEL
vda        1G
├─vda1   300M ext4
├─vda2   256M swap
└─vda3   467M ext4
vdb    931.5G
├─vdb1   250G ntfs        ELECOM USBH
└─vdb2 681.5G crypto_LUKS
time=2023-09-06T19:38:06.475+09:00 level=WARN msg="Canceling the VM context" caller=vm
time=2023-09-06T19:38:06.525+09:00 level=WARN msg="Sending poweroff command to the VM" caller=vm
time=2023-09-06T19:38:06.536+09:00 level=INFO msg="Shutting the VM down safely" caller=vm

• Attempt at mounting the LUKS partition:

linsk run -l dev:\\.\PhysicalDrive3 vdb2 ext4
time=2023-09-06T19:39:57.966+09:00 level=INFO msg="Created network tap" name=LinskTap-1693996797477168400
time=2023-09-06T19:39:57.998+09:00 level=INFO msg="Configured network tap" name=LinskTap-1693996797477168400 cidr=fe8f:5980:3253:7df4:f4b:6db1:a1d8:fc66/127
time=2023-09-06T19:39:58.046+09:00 level=WARN msg="Using raw block device passthrough. Please note that it's YOUR responsibility to ensure that no device is mounted in your OS and the VM at the same time. Otherwise, you run serious risks. No further warnings will be issued." caller=vm
time=2023-09-06T19:39:58.096+09:00 level=INFO msg="Booting the VM" caller=vm
time=2023-09-06T19:40:13.228+09:00 level=INFO msg="The VM is up, setting it up" caller=vm
time=2023-09-06T19:40:19.957+09:00 level=INFO msg="The VM is ready" caller=vm
time=2023-09-06T19:40:20.598+09:00 level=INFO msg="Mounting the device" dev=vdb2 fs=ext4 luks=true
time=2023-09-06T19:40:20.641+09:00 level=INFO msg="Attempting to open a LUKS device" caller=file-manager vm-path=/dev/vdb2
Enter Password:
time=2023-09-06T19:40:26.933+09:00 level=INFO msg="LUKS device opened successfully" caller=file-manager vm-path=/dev/vdb2
time=2023-09-06T19:40:32.577+09:00 level=ERROR msg="Failed to mount the disk inside the VM" error="run mount cmd: run cmd (log: 'mount: /mnt: can't read superblock on /dev/mapper/cryptmnt.\\n       dmesg(1) may have more information after failed mount system call.'): Process exited with status 32"
time=2023-09-06T19:40:32.577+09:00 level=WARN msg="Canceling the VM context" caller=vm
time=2023-09-06T19:40:32.624+09:00 level=WARN msg="Sending poweroff command to the VM" caller=vm
time=2023-09-06T19:40:32.634+09:00 level=INFO msg="Shutting the VM down safely" caller=vm
time=2023-09-06T19:40:33.889+09:00 level=INFO msg="Deleted network tap" name=LinskTap-1693996797477168400

For reference, I can mount that partition on a native linux machine with:

cryptsetup open /dev/sdXY cryptmnt
mount /dev/mapper cryptmnt /mnt

I tried to mount the ntfs device vdb1 instead.
While the mounting did succeed, I could not access the network share.
After entering the address into Windows Epxloror, it prompts for the username (linsk) and password (randomly generated one), but even after entering those two as per instructions, it shows:

I am not that familiar with Network Shares, so maybe I am doing it completely wrong.
Would appreciate any feedack or additional instructions on how to do this.

Suggestion for INSTALL_WINDOWS

After installing qemu using the link provided, the install path of qemu-img had to be added to the PATH environment variable of Windows, otherwise, running linsk build would throw an error along the line of could not find 'qemu-img' in %PATH%.
It might be worth mentioning to make the downstream usage experience smoother.

Suggestion for USAGE_WINDOWS

Around here, after identifying the disk of interest, it might be worth adding a note for the user to make sure that drive is not mounted by Windows.
One way to do it is to start diskmgmt, select the corresponding drive, and putting it "Offline".
There might be an equivalent wmic command, but not much time to look it up sorry.

Others

Not sure if those features are already there, or on the roadmap, but here are some things I thought would be a nice addition while trying to get it running.

• Ability to specify or fix the SMB Network share address, as well as login username and password for more persistent usage. (Namely,, I would like to keep that vdb2 partition available all the time at a fixed location. Having to log in every time with different credential is not really convenient for this use case.)

Thanks a lot for your time.
Best regards.

Hello,

I 'm on mac Apple Silicon M1 on sonoma.

I 've followed instructions in your USAGE_MACOS.md.

I am trying to mount a Volume but I cannot, I have error: "bad device name"

Here my result with linsk ls:

NAME           SIZE FSTYPE      LABEL
vda              1G             
├─vda1         160M vfat        
├─vda2         256M swap        
└─vda3         606M ext4        
vdb            2.7T             
└─vdb1         2.7T LVM2_member 
  ├─mvg-WD     500G crypto_LUKS 
  └─mvg-Media  2.2T ext4        

I want to mount mvg-Media using this command:
sudo ./linsk run dev:/dev/disk4 mapper/mvg-Media
and I have this output:

time=2024-02-01T16:57:56.977+01:00 level=WARN msg="Using raw block device passthrough. Please note that it's YOUR responsibility to ensure that no device is mounted in your OS and the VM at the same time. Otherwise, you run serious risks. No further warnings will be issued." caller=vm
time=2024-02-01T16:57:56.982+01:00 level=INFO msg="Booting the VM" caller=vm
time=2024-02-01T16:58:25.020+01:00 level=INFO msg="The VM is up, setting it up" caller=vm
time=2024-02-01T16:58:27.540+01:00 level=INFO msg="The VM is ready" caller=vm
time=2024-02-01T16:58:27.689+01:00 level=INFO msg="Mounting the device" dev=mapper/mvg-Media fs=<auto> luks=false
time=2024-02-01T16:58:27.689+01:00 level=ERROR msg="Failed to mount the disk inside the VM" error="bad device name"
time=2024-02-01T16:58:27.689+01:00 level=WARN msg="Canceling the VM context" caller=vm
time=2024-02-01T16:58:27.737+01:00 level=WARN msg="Sending poweroff command to the VM" caller=vm
time=2024-02-01T16:58:27.743+01:00 level=INFO msg="Shutting the VM down safely" caller=vm

With linsk shell, I can mount this volume with:
mount /dev/mvg/Media destination_mounted

Could you help me?

Sorry for my english

Thanks

First, thanks for doing this; it seems a clever way to approach mounting ext4 under Mac and Windows. I am running on Mac Sonoma, M2 hardware. I had to manually build qemu, which was its own story. I ended up building my own linsk as well as trying the binary available on the site; there was no difference.

There may be something obvious I am missing, but I cannot make the given command line work to mount a luks ext4 partition.

The disk has a single encrypted partition, so in linsk parlance it is vdb1. Running with mapper/vdb1 did not work; it gave a different message about not finding the disk. I ran the following:

# sudo linsk run dev:/dev/disk4 vdb1

time=2023-12-20T01:07:53.242-06:00 level=INFO msg="Booting the VM" caller=vm
time=2023-12-20T01:08:18.275-06:00 level=INFO msg="The VM is up, setting it up" caller=vm
time=2023-12-20T01:08:23.125-06:00 level=INFO msg="The VM is ready" caller=vm
time=2023-12-20T01:08:23.266-06:00 level=INFO msg="Mounting the device" dev=vdb1 fs= luks=true
time=2023-12-20T01:08:23.308-06:00 level=INFO msg="Attempting to open a LUKS device" caller=file-manager vm-path=/dev/vdb1
Enter Password: <=== TYPED AND COPIED/PASTED THE SAME KEY USED BELOW
time=2023-12-20T01:08:28.388-06:00 level=ERROR msg="Failed to mount the disk inside the VM" error="luks open: wait for cryptsetup luksopen cmd to finish (log: 'No key available with this passphrase.'): Process exited with status 2"
time=2023-12-20T01:08:28.388-06:00 level=WARN msg="Canceling the VM context" caller=vm
time=2023-12-20T01:08:28.423-06:00 level=WARN msg="Sending poweroff command to the VM" caller=vm
time=2023-12-20T01:08:28.428-06:00 level=INFO msg="Shutting the VM down safely" caller=vm

====

# cryptsetup luksOpen -d key /dev/vdb1 arch
# mkdir mnt
# mount /dev/mapper/arch mnt

and to my amazement it was mounted and accessible. I am very certain the key used was the same one that did not work with the direct command. On the direct command I tried typing it in and pasting it in, and it never worked.

I thought to post all this in case it is useful. I hope I have not wasted your and my time by not seeing the obvious, but I could not make the one line operation work. I was at least able to see that it does mount if I open it manually.

Thanks...

Hi,

When running linsk build, the qemu installation seems to encounter a network issue and is not able to reach the Alpine servers.

level=ERROR msg="Failed to set up Alpine Linux" caller=storage subcaller=imgbuilder error="run setup cmd (log: 'udhcpc: started, v1.36.1\\nudhcpc: broadcasting discover\\nudhcpc: broadcasting select for 10.0.2.15, server 10.0.2.2\\nudhcpc: lease of 10.0.2.15 obtained from 10.0.2.2, lease time 86400\\nwget: bad address 'mirrors.alpinelinux.org'\\nWarning! No mirror found'): Process exited with status 1"
A quick googling led me to this post mentioning an issue with busybox overwriting resolv.conf.

I am not sure this is the same issue, in any case, a fix would be great. Happy to provide more information if needed.

Thanks!