i started an already installed qcow2 image as in https://www.arthurkoziel.com/qemu-ubuntu-20-04/.
macos 11.0 host and ubuntu 2004 client.
Everything works fine. But i also need copy and paste throw vm and host. So i did an
apt-get install qemu-guest-agent
as descripted in https://pve.proxmox.com/wiki/Qemu-guest-agent
But the
systemctl start qemu-guest-agent
failed because of
a dependency job for qemu-guest-agent.service failed
So what was going wrong? How can i enable copy and paste?
Related
I am trying to connect my Windows 10 Home system to be able to run full Linux OS Docker containers. I have installed Docker on both WSL Ubuntu 18.04 as well as a VMware Ubuntu 18.04.
I was trying to follow this guide.
However, I get stuck trying to configure the Daemon as per the instructions.
Can’t use Docker for Windows?
This is only necessary if you are NOT running Docker for Windows!
No problem, just configure your Docker daemon to use -H tcp://0.0.0.0:2375 and --tlsverify=false. Then you can follow along with the rest of this guide exactly.
If you go down this route, I highly recommend rolling your own VM with VMware Player instead of using the Docker Toolbox because VirtualBox has crazy edge case shared folder bugs that will ruin your life at some point. Don’t worry, VMware Player is free. Just Google how to set up Ubuntu 16 server on VMware Player.
When I try to change the Docker Daemon by making a daemon.json file I get errors. I've also tried editing the .profile files and the .bashrc as per other guides (another guide), with no luck.
I am unable to check the DOCKER_HOST variable on the VM Ubuntu.
Don't make things complicated. In your case, why WSL if you just want to connect to a remote daemon? Why not simply use the windows docker client?
Setup you favorite local VM with docker.
Example: I have installed a CentOS distro running on local VMWare Workstation. All Hyper-V of course deinstalled/deactivated.
In this VM, enable tcp access for the daemon.
If you have a systemd linux distro (like mine CentOS), execute this:
sudo mkdir -p /etc/systemd/system/docker.service.d
sudo echo '[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H unix:// -H tcp://0.0.0.0:2375' >> /etc/systemd/system/docker.service.d/options.conf
sudo systemctl daemon-reload
sudo systemctl restart docker`
Test if the port is open with docker info. You should get an API access warning at the bottom result.
Download the Windows docker cli zip from here: https://download.docker.com/win/static/stable/x86_64/
Move the docker.exe to any folder, for ex. your Documents folder.
Then put this folder path into your Windows PATH variable.
Set the docker host: Open PowerShell, execute setx DOCKER_HOST <VM-IP>:2375 and close it.
Open a new PowerShell and call docker info.
You should see the docker and daemon infos.
Do what ever you like now... :-)
OK so here is what I have done so far. I installed docker for mac, and that worked fine. From there I tried to get a project up and running using docker-compose and I got the following error:
Could not read CA certificate "/Users/<useraccountfolder>/.boot2docker/certs/boot2docker-vm/ca.pem": open /Users/<useraccountfolder>/.boot2docker/certs/boot2docker-vm/ca.pem: no such file or directory
So I tried to fix it by trying this accepted answer. This is when I got another error, Host does not exist: “default”. This is when I trie this accepted answer, but when I tried to run docker-machine create default, I got this error: Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path". I am just lost at this point. Any help?
To use docker machine you need the latest version of VirtualBox, from the docker docs:
IF YOU ARE USING DOCKER FOR MAC
Docker for Mac uses HyperKit, a lightweight macOS virtualization solution built on top of the Hypervisor.framework in macOS 10.10 Yosemite and higher.
Currently, there is no docker-machine create driver for HyperKit, so you will use virtualbox driver to create local machines. (See the Docker Machine driver for Oracle VirtualBox.) Note that you can run both HyperKit and Oracle VirtualBox on the same system. To learn more, see Docker for Mac vs. Docker Toolbox.
Make sure you have the latest VirtualBox correctly installed on your system (either as part of an earlier Toolbox install, or manual install).
Source: https://docs.docker.com/machine/get-started/#prerequisite-information
OK so I found a solution which is probably not fixing the root issue, but it does work. To unset previous variables I ran this command unset ${!DOCKER*}. This worked, but then I had to run it every time I started a new terminal session, so I added it to my .bash_profile and now I am good.
I have managed to install docker into my machine which is using Windows 7. My machine is under corporate network. As i am trying to learn docker i was following this guide. When my Dockerfile is executing:
RUN apt-get -y update && apt-get install -y fortunes
which is perform ubuntu update and installing fortunes i get the following error:
cannot initiate the connection to archive.ubuntu.com:80. and - connect <101:network is unreachable>
In order to solve my problem, first i connected to my vm machine and i located the /etc/resolv.conf file where i modify it to add google dns
namespace 8.8.8.8
but that seems to not solve the issue when i exited and rebuild my Dockerfile.
As my machine is on windows i haven't found a solution for this problem. Does anyone know how should i surpass this problem?
You have to start your dockerd (docker daemon) with same nameserver of your windows computer network settings and then your container and image will get the connectivity from outside network/internet.
For more details Please visit this official link from docker :https://docs.docker.com/docker-for-windows/#network
I started Docker and am now following the tutorial, but for all I know I couldn't run the docker-machine command on OS X.
The documentation states that you run the following command to create a local virtual machine:
docker-machine create --driver virtualbox manager
However, this command doesn't work in OS X (11.6), with the following error:
Running pre-create checks...
Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"
I tried to install the virtualbox; however, another page clearly states that you must not install it on your local machine:
VirtualBox prior to version 4.3.30 must NOT be installed (it is incompatible with Docker for Mac)
Note: If your system does not satisfy these requirements, you can install Docker Toolbox, which uses Oracle VirtualBox instead of HyperKit.
So I only installed Docker for Mac and not virtualbox. So what am I missing here? The example page says you can run the tutorial on OS X, so I wonder how I can proceed...
You can follow along and run this example using Docker for Mac, Docker for Windows or Docker for Linux.
I had the same issue today and resolved it by installing VirtualBox as an additional step after installing Docker for Mac (I did so with brew install --cask virtualbox)
I don't recall having to do the extra install previously, but maybe I already had VirtualBox already installed because of another tool (like Vagrant). Anyway, this is explained in the Docker Machine documentation:
If you are using Docker for Mac
Docker for Mac uses HyperKit, a lightweight macOS virtualization
solution built on top of the Hypervisor.framework in macOS 10.10
Yosemite and higher.
Currently, there is no docker-machine create driver for HyperKit, so
you will use virtualbox driver to create local machines. (See the
Docker Machine driver for Oracle VirtualBox.) Note that you can run
both HyperKit and Oracle VirtualBox on the same system. To learn more,
see Docker for Mac vs. Docker Toolbox.
Make sure you have the latest VirtualBox correctly installed on your system (either as part of an earlier Toolbox install, or manual
install).
I had the same issue. At the same spot ;-)
For me the xhyve driver, available from https://github.com/zchee/docker-machine-driver-xhyve, worked.
In short:
brew install docker-machine-driver-xhyve
You get a notice some links need to be created manually, so copy those and execute
sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
Create:
docker-machine create --driver xhyve manager
Without VirtualBox. Im using OS X 10.11.6, too.
After updating my docker docker-machine command stopper working on my mac terminal.
So found after updating my docker I'll have to reinstall docker-machine CLI just to get the latest version.
Updated docker-machine to latest one using the command below helped me making docker-machine command working again.
base=https://github.com/docker/machine/releases/download/v0.16.0 &&
curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/usr/local/bin/docker-
machine &&
chmod +x /usr/local/bin/docker-machine
See Docs (https://docs.docker.com/machine/install-machine/#install-machine-directly)
I'm trying to automate a download of a 3 gig file into a vm managed by using vagrant and puppet. The file downloads, and appears to be the full three gigs, but the md5 I download with it consistently fails the md5sum test. Conversely, if I download it outside the vm on my mac (with wget) into a shared folder with the vm, and then ssh into the vm and check the md5 it downloads fine. Any suggestions?
Code example:
wget http://mymachine.com/archive.zip && wget http://mymachine.com/archive.md5
md5sum -c archive.md5
What I'm running:
Local Machine: Mac OSX Mavericks
VM OS: CentOS 6.4
Vagrant Version: 1.3.5
VirtualBox Version: 4.3.4
I would run the problematic wget with the -d flag on its own.
Review http://www.gnu.org/software/wget/manual/wget.html#Reporting-Bugs for more info on finding out what is happening for wget.
This may give you some clues as to why this does not work in the VirtualBox VM
Then you will need to review https://forums.virtualbox.org/viewtopic.php?f=24&t=48476
to review the steps required to query Virtual Box logs to report probelems with it.
Finally, you could try older versions of Virtual Box to see if the problem still occurs.
Hope this helps.
I was having the same problem with a very similar configuration and downgrading to VirtualBox 4.2.24 works for me as a workaround.
Host Hardware: MacBook Pro
Host OS: Mac OS X Mavericks (10.9.2)
Guest OS: CentOS 6.4
Vagrant: 1.4.3
VirtualBox: Tried 4.3.6, 4.3.8, 4.3.10 and they all resulted in corrupted wget downloads inside the guest OS for large zip files (600MB - 1.2GB)
Not sure what is going on as I thought VirtualBox 4.3.+ added better Mavericks support.