Installed podman using brew (brew install podman)
Trying to start the VM using podman machine init but receiving the following error:
Extracting compressed file
Error: cannot overwrite connection
Info:
$ podman machine ls
NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE```
$ brew info podman
podman: stable 4.1.0 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
/usr/local/Cellar/podman/4.1.0 (174 files, 48.2MB) *
Poured from bottle on 2022-06-09 at 15:49:37
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb
License: Apache-2.0
==> Dependencies
Build: go ✘, go-md2man ✘
Required: qemu ✔
==> Options
--HEAD
Install HEAD version
==> Caveats
zsh completions have been installed to:
/usr/local/share/zsh/site-functions
==> Analytics
install: 19,856 (30 days), 60,723 (90 days), 152,955 (365 days)
install-on-request: 19,746 (30 days), 60,606 (90 days), 152,824 (365 days)
build-error: 1 (30 days)
sw_vers
ProductName: macOS
ProductVersion: 11.6.6
BuildVersion: 20G624
I have uninstalled and reinstalled using brew, does not change.
Had docker on machine, uninstalled it completely, restarted my machine and tried again reinstalling podman with brew. The problem remains.
Any pointers, instructions how to resolve it appreciated greatly. Thank you.
Resolved the issue by following these steps:
Removed podman brew uninstall podman
Removed containers files from the following directories:
rm -rf ~/.config/containers/
rm -rf ~/.local/share/containers
Reinstalled podman using brew brew install podman
Init the podman machine and start it.
In addition to #Simas Answer: https://stackoverflow.com/a/72571826/3596851
After removing the container files
rm -rf ~/.config/containers/
rm -rf ~/.local/share/containers
I had to remove additional Podman related files:
rm ~/.ssh/podman*
Then I reinstalled Podman brew install podman, followed by init podman machine init, and podman machine start. This worked for me
Related
I find a tutorial to install BetterCap on Ubuntu Linux at
You tube tube tutorial
Can some one do a favor of adopting them to Mac Big Sur ver 11.0
When I run them, it is not able to recognise Java Run time even though 3 instances are present.
/usr/libexec/java_home -V
Matching Java Virtual Machines (3):
17.0.1 (x86_64) "Homebrew" - "OpenJDK 17.0.1" /usr/local/Cellar/openjdk/17.0.1_1/libexec/openjdk.jdk/Contents/Home
1.8.0_312 (x86_64) "Homebrew" - "OpenJDK 8" /usr/local/Cellar/openjdk#8/1.8.0+312/libexec/openjdk.jdk/Contents/Home
1.8.0_312 (x86_64) "Amazon" - "Amazon Corretto 8" /Users/venkatanutalapati/Library/Java/JavaVirtualMachines/corretto-1.8.0_312/Contents/Home
/usr/local/Cellar/openjdk/17.0.1_1/libexec/openjdk.jdk/Contents/Home
The detailed steps in the description are...
- sudo apt update
- sudo apt install libpcap-dev libusb-1.0-0-dev libnetfilter-queue-dev
- wget https://github.com/bettercap/betterca...
- unzip bettercap_linux_amd64_v2.26.1.zip
- sudo mv -v bettercap /usr/bin
- rm -rf bettercap_linux_amd64_v2.26.1.*
Bettercap seems to have a homebrew formulae - just try to run brew install bettercap and it should install it for you. No need to get it directly from git and follow all of these steps
I'm trying to follow Install Minikube and even though there are no errors during install, I still unable to run it:
$ brew install minikube
Updating Homebrew...
==> Downloading https://homebrew.bintray.com/bottles/minikube-1.5.2.catalina.bottle.tar.gz
Already downloaded: /Users/alexus/Library/Caches/Homebrew/downloads/a466d3b5c7208788bb6a82fa4de4576440dbfa3b7b5b1d4ddb48cb9a3d44f1e9--minikube-1.5.2.catalina.bottle.tar.gz
==> Pouring minikube-1.5.2.catalina.bottle.tar.gz
==> minikube cask is installed, skipping link.
==> Caveats
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
zsh completions have been installed to:
/usr/local/share/zsh/site-functions
==> Summary
🍺 /usr/local/Cellar/minikube/1.5.2: 8 files, 51.5MB
$ minikube
-bash: minikube: command not found
$
Please advise.
$ sudo mv minikube /usr/local/bin
Password:
mv: rename minikube to /usr/local/bin/minikube: No such file or directory
$
minikube version:
$ /usr/local/Cellar/minikube/1.5.2/bin/minikube version
minikube version: v1.5.2
commit: 792dbf92a1de583fcee76f8791cff12e0c9440ad
$
Try using
brew link minikube
which solved the issue for me. After installing minikube using Homebrew (brew install minikube) we need to run the above command which will create symlinks for us. Then the minikube command works fine.
This looks like an issue with your path:
Restart the terminal.
Did you add minikube to the path per the documentation?
Here’s an easy way to add the Minikube executable to your path: sudo
mv minikube /usr/local/bin
Verify the path with which minikube.
Edited to address new info in questions:
This is still a path issue. It appears that your install went to /usr/local/Cellar/minikube/1.5.2 not /usr/local/bin/minikube. The different aliases are looking for the latter directory which is why this is not working for you. You should move the directory as per the documentation so that the scripts with the various shortcuts can find the proper link.
my way of solving this:
$ cd /usr/local/Cellar/minikube/
$ sudo ln -s 1.5.2 current
Password:
$ cd /usr/local/bin/
$ ln -s /usr/local/Cellar/minikube/current/bin/minikube
$
$ minikube version
minikube version: v1.5.2
commit: 792dbf92a1de583fcee76f8791cff12e0c9440ad
$
This helped me on ubuntu:
sudo ln /home/linuxbrew/.linuxbrew/Cellar/minikube/1.28.0/bin/minikube /usr/local/bin
To discover if your path to minikube differs, use:
$ brew link minikube
Seems brew fails to uninstall protobuf completely:
brew uninstall protobuf --force
brew uninstall protobuf#3.1 --force
brew info protobuf
protobuf: stable 3.6.1 (bottled), HEAD
Protocol buffers (Google's data interchange format)
https://github.com/protocolbuffers/protobuf/
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/protobuf.rb
==> Dependencies
Build: autoconf ✘, automake ✘, libtool ✔
Recommended: python#2 ✔
Optional: python ✘
==> Options
--with-python
Build with python support
--without-python#2
Build without python2 support
--HEAD
Install HEAD version
==> Caveats
Editor support and examples have been installed to:
/usr/local/Cellar/protobuf/3.6.1/share/doc/protobuf
==> Analytics
install: 20,550 (30 days), 75,916 (90 days), 307,704 (365 days)
install_on_request: 10,362 (30 days), 36,197 (90 days), 141,839 (365 days)
build_error: 0 (30 days)
brew uninstall protobuf
Error: No such keg: /usr/local/Cellar/protobuf
protoc
-bash: /usr/local/opt/protobuf#3.1/bin/protoc: No such file or directory
What is the proper way to uninstall it completely?
It’s not Homebrew’s fault: it’s Bash’.
When you type protoc, Bash searches the executable in your PATH. In your case, it’s /usr/local/opt/protobuf#3.1/bin/protoc. However, it only does that the first time: it caches its findings for the session.
You uninstalled protobuf and so Homebrew removed the /usr/local/opt/protobuf#3.1/bin/protoc file; but you haven’t cleared Bash’ cache, so it still thinks this file exists.
The solution is to either start a new shell session or force Bash to clear its cache with hash -r.
Illustration:
$ touch /tmp/hi
$ chmod u+x /tmp/hi
$ export PATH="/tmp:$PATH"
$ which hi
/tmp/hi
$ hi # <-- executes /tmp/hi and cache hi=/tmp/hi
$ rm /tmp/hi
$ hi # <-- still executes /tmp/hi because of the cache
bash: /tmp/hi: No such file or directory
$ hash -r # clear the cache
$ hi
hi: command not found
I installed Docker on my Mac OSX machine (El-Capitan) using Homebrew.
But when I try to run it, it gives me the error shown below.
$ docker --version
Docker version 17.06.0-ce, build 02c1d87
$ docker-compose --version
docker-compose version 1.14.0, build unknown
$ docker-machine --version
docker-machine version 0.12.2, build 9371605
$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
Is the docker daemon running?
How can I fix it?
There is no need to uninstall docker, I hit this hurdle as well and on Mac, follow these steps
Go to the application folder and click the docker icon
wait for it to start
Once the docker starts, you can run any docker command without any issue
It looks like you need to start the Docker daemon first. Check the caveats section of brew info docker-machine.
$ brew info docker-machine
docker-machine: stable 0.12.2 (bottled), HEAD
Create Docker hosts locally and on cloud providers
https://docs.docker.com/machine
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/docker-machine.rb
==> Dependencies
Build: go ✔, automake ✔
==> Requirements
Build: git ✔
==> Caveats
To have launchd start docker-machine now and restart at login:
brew services start docker-machine
Or, if you don't want/need a background service you can just run:
docker-machine start
I had installed minikube a few months ago and wanted to upgrade as newer versions are available.
I am unable to find out how to upgrade minikube. I see a feature request for an upgrade command here - https://github.com/kubernetes/minikube/issues/1171
I tried to then uninstall minikube and hit another brickwall again. I don't see a command to uninstall minikube. The information that came closest to this was not very helpful - https://github.com/kubernetes/minikube/issues/1043
I guess we need ways to upgrade these (at least once every 6 months or so).
Before reinstall minikube (OS X), check the following:
Make sure that you have brew updated:
brew update
Make sure that you already have cask installed:
brew cask install minikube --verbose
Finally, execute the following command in the same directory you've installed minikube previously (usually /usr/local/bin/):
brew cask reinstall minikube
If you see an output similar to this:
Error: It seems there is already a Binary at '/usr/local/bin/minikube'; not linking.
Remove the existing binary:
rm /usr/local/bin/minikube
Now, you should able to reinstall (upgrade) minikube. :)
brew upgrade minikube
Just upgrade minikube with brew
This should do the trick.
brew cask reinstall minikube
First, unlink the existing minikube from /usr/local/bin then reinstall:
$ sudo rm -rf /usr/local/bin/minikube # unlink existing minikube
$ brew update # update brew itself
$ brew cask reinstall minikube # reinstall latest minikube
An updated way is to use this:
brew cask upgrade minikube
Process to update:
Minikube is an executable: Re-install minikube is an upgrade.
Optionally you can remove ~/.minikube which will make minikube completely re-initialize and also update your kubernetes version (if a new version has been made available for minikube).
minikube delete
sudo rm -rf ~/.minikube
re-install minikube and it should work
if you are using Windows machine and Chocolatey package manager -
Step 1: run PowerShell as administrator
Step 2: run following command choco upgrade minikube
More on chocolatey https://chocolatey.org/
As of early 2020, and based on the guidance provided by this answer, minikube is no more available as a cask. You need to run:
brew install minikube
Minikube is no longer available in cask and calling brew cask while performing install, upgrade, or reinstall is deprecated! Use the below syntax instead:
Make sure brew is updated:
brew update
Then, to install, use:
brew install minikube
To upgrade, use:
brew upgrade minikube
To reinstall, use:
brew reinstall minikube
If you're reading this in 2020+:
brew upgrade minikube
On linux:
curl -Lo minikube https://storage.googleapis.com/minikube/releases/v1.22.0/minikube-linux-amd64 && chmod +x minikube && sudo cp minikube /usr/local/bin/ && rm minikube
Change the version you want to download. Above script uses 1.22.0
Just try brew upgrade minikube
brew reinstall minikube --cask did the trick for me
In order to upgrade in Windows, type:
minikube start
The following is the output you will get (make sure you are connected to internet):
Here is a newer version of Minikube available (v0.28.0). Download it here:
https://github.com/kubernetes/minikube/releases/tag/v0.28.0
if you don't get the above message then first run
minikube config set WantUpdateNotification true
then do,
minikube start
Before that, remove all the Minikube links from the system:
Remove the previous installation path.
From this folder, remove c:\Users\<user-name>\ .kube folder.