-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vagrant alternatives? Docker? Blocked by M1/M2 issues #510
Labels
Comments
See #404 - One option is Tart, though it's not currently as easily automatable as Vagrant + VirtualBox (though efforts are being made). The one challenge to the Docker approach is there's no networking support to make it behave like real VMs/machines with dedicated IP addresses, so the networking model breaks a bit (compared to Docker-style/container deployments). But we'll see. All the discussion should end up in #404 though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Jeff,
Great book, but I'm completely blocked from using it. Can't use Vagrant in the legacy / air-gapped Intel environment I'm working in, and every other system I have is M1/M2.
I noticed you too were struggling with this: #404 Did you ever find a way around it?
I can use docker / podman. Basically, looking for the equivalent 'docker-compose.yml' versions of all your Vagrant scripts from Ch03 on. Have you been working on anything like that or can you suggest alternatives?
Thanks,
Blue
The text was updated successfully, but these errors were encountered: