I have done the following so far:
brew install qemu (apparently needed for podman, but want to use it for VMs anyway)
brew install podman
modify ~/.config/containers/containers.conf and add following line to [engine] section:
helper_binaries_dir = ["/Users/user/dev/homebrew/Cellar/podman/4.1.0/bin","/Users/user/dev/homebrew/Cellar/podman/4.1.0/libexec"]
podman machine init
podman machine start
Initially, machine start complained it could not dial up a unix socket at var/folders/v0/xqf571mj5sg5x7k4j1dpb1_w0000gn/T/podman/podman-machine-default_ready.sock. That file existed, so don't know what the problem was.
I rebooted to see if that would help, and now that socket file no longer exists, but podman machine start still wants to use it. Rerunning podman machine init just gives this error:
Error: podman-machine-default: VM already exists
That error always occurs once it successfully inits, so doesn't seem to be related to my issue.
That's as far as I can get from various web pages I read. Hopefully someone can provide further help :)
I've been away from using a Mac for over a decade, so really have no idea how stuff like podman is supposed to work, beyond it apparently needs QEMU to run a VM for each container.
Am I better off using Docker Desktop for Mac instead of fighting with podman? If so, I'll just use that. Podman was butt easy on my Linux desktop, but maybe it's not worth the trouble on a Mac, or at least on an M1 since it's an arm.
I had a similar issue yesterday, as have others. The solution comes from the issue thread linked in the comment above. The problem was resolved by downgrading the version of QEMU from the one currently available as default on homebrew.
You can downgrade to QEMU 6.2.0 on Monterrey with the following:
curl -L -H "Authorization: Bearer QQ==" -o qemu-6.2.0_1.monterey.bottle.tar.gz https://ghcr.io/v2/homebrew/core/qemu/blobs/sha256:fcc3b1a8139f70dae57f5449f3856f9b3b67448ee0623e64da1e47dc255b46f6
brew install -f qemu-6.2.0_1.monterey.bottle.tar.gz
After some time debugging, I found the cause of this problem.
This problem is caused due to qemu 7.0.0 startup latency (3-5s) that occour in every first qemu execution after Mac Machine machine boots.
Podman has some bug that doesn't expect that the creation of socks files, done by the qemu call, can be delayed some seconds, and when podman tries to access the socks files, the qemu is not created them yet, showing the error "Error: dial unix /podman/podman-machine-default_ready.sock: connect: connection refused".
To avoid this problem, just execute qemu, even with invalid options (just to initialize), before call "podman machine start".
After some time debugging, I found the cause of this problem.
This problem is caused due to qemu 7.0.0 startup latency (3-5s) that occour in every first qemu execution after Mac Machine machine boots.
Podman has some bug that doesn't expect that the creation of socks files, done by the qemu call, can be delayed some seconds, and when podman tries to access the socks files, the qemu is not created them yet, showing the error "Error: dial unix /podman/podman-machine-default_ready.sock: connect: connection refused".
To avoid this problem, just execute qemu, even with invalid options (just to initialize), before call "podman machine start".
echo "* Podman VM machine for MACOSX is stoped, starting..."
# workaround - initialize qemu before machine start to avoid socket error
/usr/local/bin/qemu-system-x86_64 -machine q35,accel=hvf:tcg -cpu host -display none INVALID_OPTION >> /dev/null 2>&1
podman machine start podman-machine-default
ECODE=$?;if [ $ECODE -ne 0 ];then echo "* Error starting podman linux vm machine: $ECODE";exit $ECODE;fi
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?
I'm currently trying to bind a cmd shell in Windows using ncat with SSL in order to allow a Kali Linux computer to connect.
On the Windows computer, I run
ncat --exec cmd.exe --allow KaliLinux.computer -vnl PortNumber --ssl
On the Kali Linux computer, I then run
ncat -v Windows.computer PortNumber --ssl
I am then prompted on the Kali Linux terminal:
Ncat: Certificate verification failed (self signed certificate).
However, I am still greeted with the Windows CMD output.
On attempting to run any sort of command over this ncat connection, no response is retrieved from the Windows computer and looking at the CMD screen on the Windows computer reveals the connection has closed without any warning/errors.
If I attempt the same without the --ssl flag, the binding and connection works as intended.
My query is, how do I override the certificate verification failed notification or how do I create a valid and secure SSL connection such that the connection works?
Check if your SSL version in both your Windows VM and Kali Linux are compatible. ncat 7.60 doesn't support tls 1.2 anymore.
The other way around is to use OpenSSL instead of ncat on your Kali Linux (you can still use ncat in your Windows VM).
E.g. openssl s_client -connect 10.0.0.2:4444
I have tried installing docker/boot2docker on my mac and no matter what I do I cannot get it through the "up" process.
I tried installing via brew
- That did not work, so I uninstalled everything
I tried installing via the docker site (package that installs VirtualBox, Docker, Boot2Docker)
- again, when I try "up" it just hangs and will not finish.
This should not be an issue because I tried this install after reformatting my hard drive ...
I have tried all of the 'solutions' that have been suggested all over the web, from checking my etc/hosts file so that "127.0.0.1 localhost" is there to going into VirtualBox deleting the VM then running "init" again... all the way to uninstalling absolutely everything on my computer and trying a fresh install ...
When I do the docker command "up" it just hangs. Not once have I made it to the end of this process. This is the line it hangs on and repeats over and over again:
.Connecting to tcp://localhost:2022 (attempt #0)2015/03/21 19:49:47 executing: /usr/bin/ssh ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -p 2022 -i /Users/me/.ssh/id_boot2docker docker#localhost ip addr show dev eth1
Prior to reformatting my hard drive, I had this installed before without any issues. I do not remember the version I had installed, but my guess is that it was not v1.5.0.
After trying for nearly 13 hours to get this to work, I am pretty much ready to throw in the towel and be done with it unless someone can tell me how to get it to work.
I have been a Windows user all my life and I just got a Mac recently. With Windows (puTTY), I have "SSHed" into a local Ubuntu Server dozens of times in the past. I attempted to perform the same steps with my Mac, but I am not able to make any significant progress. Can anyone provide a guide as to how to SSH into a local Ubuntu Server?
I have a clean installation of Ubuntu Server running right now. Here is a picture of when I do "ifconfig":
The steps that I have done previously are as follows:
Install openSSH Server
In terminal, "ssh anish#localhost"
Connection is timed out or my password is not accepted.
Change it to bridged in ur VM settings in virtual box and use ssh anish#inet