I have just succesfully installed Arch Linux on my Laptop that also runs windows 10. My problem is that there is no visible boot menu where I can choose my os, it always just starts windows. when I run
cfdisk
it lacks the option of adding a bootable flag to my linux partition.
Is there any way of adding a boot menu?
Thanks in advance
Check out Dual boot with windows
You can install system-boot
mount /dev/sda5 /mnt
mkdir /mnt/boot
mount /dev/sda2 /mnt/boot #mount EFI
run this command to install bootloader
bootctl install
And then
cp /usr/share/systemd/bootctl/arch.conf /boot/loader/entries/
Now just modify the arch.conf and enjoy your archlinux.
Related
I want to run Windows 10 on Windows 10 with QEMU (not with other software). I downloaded QEMU, and set up environment variable. I also got the Windows 10 iso file, renamed it to win10.iso, and put that in the same directory as the QEMU folder. Then I ran this command in the QEMU folder with cmd prompt: qemu-system-x86_64.exe -boot d -cdrom win10.iso -m 2048
It worked fine, but when it asked for the drive, I got confused. image.
I clicked on the first option, and it said this. So clicked on the second option, and it gave me this. I clicked "load driver" and it gave me this. How do I make a device driver?
You misunderstood windows installer. The window on the first image asks you for installation type - installing a new version or upgrading an existing. The upgrade option is only available when you have an installed version and runs the installer from a booted windows, not when booting from installation media. So installing a new version is your choice. The window on third image says windows installer cant find any disks where it can install the OS. This is because you ran qemu with a cdrom and no disks. The solution here is not to load a driver, but run qemu with a hard disk.
First create a disk, for example so:
qemu-img.exe create -f qcow2 win10.qcow2 50G
Then run qemu with this disk:
qemu-system-x86_64.exe -boot d -cdrom win10.iso -m 2048 win10.qcow2
I'm running docker for mac and want to start up a windows container. From what I see this should work via a virtual machine. But I'm unclear where to find out how to get it to work? Or does it only work for linux containers? Thanks in advance!
docker build nanoserver/
Sending build context to Docker daemon 2.56kB
Step 1/6 : FROM microsoft/nanoserver:10.0.14393.1480
10.0.14393.1480: Pulling from microsoft/nanoserver
bce2fbc256ea: Pulling fs layer
baa0507b781f: Pulling fs layer
image operating system "windows" cannot be used on this platform
I know I am late to the party but as of 2021, this is the easiest setup to get a windows container running on macOS:
https://github.com/StefanScherer/windows-docker-machine
Install vagrant and virtual box
Clone the repository above and change directory into it
vagrant up --provider virtualbox 2019-box
docker context use 2019-box
I followed this setup and I could use the following windows image
mcr.microsoft.com/windows/servercore:ltsc2019
Please note that the windows version of your host must match the container image. This is mentioned here: https://hub.docker.com/_/microsoft-windows
Windows requires the host OS version to match the container OS
version. If you want to run a container based on a newer Windows
build, make sure you have an equivalent host build.
See this link:
https://forums.docker.com/t/how-do-i-start-a-windows-docker-container-on-my-mac-os-x/12953/2
Text if you can't follow the link:
On OS X, get VirtualBox.
Get Windows Server 2016 Tech Preview 5 ISO167 (free download from Microsoft)
Create WS 2016 TP5 VM in virtualbox
Run this206 in the new VM
Now you can run Windows Containers in the VM. To make the setup a little easier to use, see this: https://forums.docker.com/t/windows-server-2016-tp5-docker-server-remote-management/10315/5317
You could also install Bootcamp on your machine which allows you to dual boot your computer between OS X and Windows 10. You could then use the full power of your hardware dedicated to Windows and docker instead of virtualization.
Additionally, you can make the use of VMWare Fusion for Mac OS or Parallels, which allow you to ALSO access the dual boot windows partition from within the Mac OS for maximum flexibility. During installation make sure you do not create a Virtual Machine drive, but instead access the bootcamp partition directly.
Read-Only File System after Upgrade Kernel under CentOS 7
Hi all,
I upgraded the kernel of CentOS 7 to 4.11.4, and reboot the VM. After that, I cannot change anything in the system. No matter what I do, it says Read-only file system.
I want to work with the latest kernel, what's the correct way to upgrade kernel under CentOS 7 on Google Cloud Engine?
Thank you very much!
Try remounting the filesystem
sudo mount -o remount,rw /dev/sda3
I have a Mac running OSX El Capitan, which cannot easily mount a Linux ext3 filesystems. I have a USB drive with exactly this file system and need to access.
OSXFUSE + Ext2 FUSE module seems not to work as I have installation errors that might be related to El Capitan being too new (the Ext FUSE module conplains about that at least). There is another commercial product, called Paragon ExtFS, that throws me similar problems for the trail version.
Now, I am thinking of an alternative by using VirtualBox, with an Ubuntu 14.04 that mounts the drive.
I added the following line to /etc/fstab
/dev/sdb1 /media/mystuff ext3 defaults 1 2
but rebooting my machine makes no difference. I have to add that this USB drive is USB3.
What am I doing wrong? Can I technically mount a USB drive that Mac per standard does not understand?
Yes, you can mount ext3 in Ubuntu running in VirtualBox on your El Capitan.
That's what worked for me (I had 12.04, but it shouldn't matter):
Get the latest VirtualBox and VirtualBox Extension Back from https://www.virtualbox.org/wiki/Downloads
Make sure your Ubuntu has been shut down, navigate to virtual machine Settings -> Ports -> USB
Enable USB Controller, choose USB2.0 just in case as most USB3 devices are backwards compatible. Add your device to the list.
Start your Ubuntu, log in and check for devices:
sudo fdisk -l
Make sure you have ext3 as System. It may also be Linux LVM nowadays. If so, proceed with https://superuser.com/a/116634
mount manually:
sudo mount /dev/sdb1 /media/mystaff
I have Docker installed on Windows 7 platform. However when I try to run boot2docker start, the console gives me:
Failed to get machine 'boot2docker-vm': machine does not exist.
Ok, so I try to initialize the machine: boot2docker init. What now happens is even though I have the ISO image on the same path as docker, it tries to download a new image (and then fails to do so).
I uninstalled both OracleVM and GIT before installing them with boot2docker bundle as advised on Docker forums, but now I don't know how to proceed.
I had the same problem on a Windows 7 64 bit system when I installed the entire boot2docker package. It seems that running the solely 64-bit based boot2docker image from a 32-bit OS image (e.g. created by Virtualbox) does not work.
The solution for me was
to activate Intel Virtualisation Technolologies in my BIOS
(Lenovo X61 for me). Note that the settings can be found either
under CPU or Security.
choose a 64 bit OS version in VirtualBox and boot in with the
image obtained by boot2docker.
In case you're trying to do this now
For Windows 10 64-bit: Pro, Enterprise, or Education (Build 15063 or later), follow the instructions to install Docker Desktop here https://docs.docker.com/docker-for-windows/install/.
If you have Windows systems that do not meet the requirements of Docker Desktop for Windows(in my case Microsoft Windows 10 Home Single Language), you can install Docker Toolbox by following the instructions here https://docs.docker.com/toolbox/toolbox_install_windows/.
boot2docker does not support sharing directories on Windows IIRC. The way I run Docker on windows is:
install VirtualBox
install Vagrant
create a directory (let's say c:\vm\docker)
download this Vagrantfile and save it under c:\vm\docker\Vagrantfile
open a DOS command prompt
go to the directory cd c:\vm\docker
start the VM vagrant up and wait for it to install, start up and get provisionned
connect to the VM vagrant ssh
play with docker docker images, etc
Also you might want a real console instead of using the DOS command prompt:
install Git Bash for Windows
install Console
setup Console to use Git Bash (see this guide)
use Console to run the vagrant up and vagrant ssh commands