Home Assistant in Docker on MacOs BigSur

 

  1. Install brew. Follow instructions on https://brew.sh/

  2. Install virtualbox

    1. # brew install virtualbox

  3. Install docker-machine

    1. # brew install docker-machine

    2. # brew services start docker-machine

  4. If you want the machine to run at boot (rather than at login)

    1. Move your launchd configuration file homebrew.mxcl.docker-machine.plist from $USER/Library/LaunchAgents to /Library/LaunchDaemons

    2. Add a user directive: 

<key>UserName</key>

<string>robcos</string>

    1. Make sure the permissions are right:

# sudo chmod root.wheel homebrew.mxcl.docker-machine.plist

  1. Install docker

    1. # brew install docker

  2. Create a virtual machine

    1. # docker-machine create --driver=virtualbox default

  3. Setup docker environment (you will need this every time you open a new shell)

    1. # eval $(docker-machine env default)

  4. Setup your “default” virtualbox to forward any relevant port. 

    1. Settings -> Network -> Adapter 1 -> Nat -> Advanced

In my case I forward 1880 for NodeRed, 8123 for HomeAssistant and 8080 for Apache

Comments

Post a Comment

Popular posts from this blog

The little yellow book of vaccinations

Image
I have almost filled my yellow book with vaccinations. You get it when you contact NHS and make an appointment with your closest travel clinic. I went to my usual surgery Sterndale in Hammersmith. The nurse recommended to get Hepatitis A and B, Typhoid, Rabies and the compulsory Yellow Fever. Some of them require more than one shot so make sure to start your treatment at least 3 weeks before you leave. I am also going to get an anti malaria treatment but for that I need another appointment. The injection are almost harmless so don't be scared. Be scared of the bill though as some of those vaccines are not free and cost up to 40£ per short. And yes, you can also use private clinics as Nomad (STA Travel) but it will cost you more.
Read more

ReadyNas NV+ and rsync

Setting up an account to backup a windows machine to my Nas I discovered an issue with the rsync setup. I first enabled the rsync protocol in the readynas admin interface. I then added a new user account and when I was testing I got the following error: rsync -av myidr/ newuser@mynas: newuser@mynas's password: Connection closed by 192.168.1.100 rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-35.2/rsync/io.c(452) [sender=2.6.9] I tracked down the problem to not having a ssh key on the nas for the new user: su - newuser Password: newuser@mynas:~$ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/c/home/newuser/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in . Your public key has been saved in .pub. The key fingerprint is: c1:25:12:5b:21:18:31:23:73:58:45:99:2c:0b:0e:7c newuser...
Read more