Clean new mac install docker issues #7
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: octoleo/octojoom#7
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I tried it on my wifes laptop and it failed to install docker correctly.
Hmm this was caused by a previous try to install docker without using --cask. I removed all files to clean it up and then it worked fine. But on MACOS you need docker desktop (it's what get installed through command line) and you'll just open docker desktop app after installation to get the docker daemon running. Then you can use octojoom to install traefik, portainer and you're set.
So are you saying we should replace:
With:
Give me the guidance that will work on MACOS (any version)
This also goes for:
What will be the correct way for Docker Compose
I will have to test again and clean it first but i don't think compose is a gui application so you won't have any issues. when i tried installing it before it seemed to work fine. will try to clean it up best i can and then try to test again.
note this in the error:
Which means there is still an installation, and the
open /Applications/Docker.app
might not be the correct way.Remember I am not on Mac, nor do I have any to test this... so your input here is very helpful, thanks!
That was exactly the issue. cleaning up the files in use/local/bin fixed it. it was causes by running brew install docker instead of brew install --cask docker. I must've done it on this laptop in the past i guess. Cleaning it and doing it again it works just fine.
After octojoom finishes installation the macOS will ask me to open docker app.
Okay so this means I don't change anything here right, if so please close the issue.
indeed :)