search

vigeeking / homeAutomation

My goal is to create a pipeline that is built exclusively with tools I either already know, or am only learning because they provide added value to the project
https://github.com/vigeeking/homeAutomation
0 stars 0 forks source link

Look into pi vm as dev environment. #41

Closed vigeeking closed 4 years ago

vigeeking commented 4 years ago

I suspect I will be doing more with system creation and automation. The first staging ground for a lot of these ideas will be raspberry pi's... I'm a dumbass. Why haven't I looked into a pi vm? Change story, but keeping thought process for later examination and lessons learned. Instead of making the pi creation process easier, why not look into just using virtual pi's for a dev environment.

This is related to ticket #14

vigeeking commented 4 years ago

I have decided to use virtualbox as my vm host for the time being. I have set up a natted network in virtualbox, I THINK I have done this correctly, but that is an assumption. For now I am basing the dev natted network with the same ip pool as my home lab. This presents theoretical problems with ip conflicts later, but also presents a potential point to hot swap. For now I am accepting the friction from the possible IP conflict.

vigeeking commented 4 years ago

Since I am using raspbian desktop as my vm, I was running into some issues getting docker working due to architecture difference. I manually installed the linux version, and then to get docker-compose working I used this script: https://gist.github.com/blazewicz/04e666ae1f25387c8b291d81b12c550c rename this script to .sh and run it. dockerComposeForPiVM.txt

vigeeking commented 4 years ago

network settings for virtualbox.docx

These are the main steps I've taken in shorthand to get the NAT working with the pi vm.

vigeeking commented 4 years ago

Pi VM created, and successfully pulled image and loaded hassio after adding ports to nat table.