Replies: 1 comment
-
Hey @robbiemu you got this up and running? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to repurpose an M1 Mac as a sort of light-weight, local dev cloud environment.
So right now I have an Azure SDK demo project that is a cloud function that just returns what it is given. And of course I have a virtual machine to run it in, defined by this handy script:
podman-init.up.sh
#!/bin/sh
PATH=/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin PODMAN_INIT_PATH=/Users/Shared/source/podman-init IGNITION_FILE=$PODMAN_INIT_PATH/ignition.json podman machine init --cpus 4 \ --disk-size 128 \ --memory 8196 \ --rootful \ --volume /Users/Shared/volumes/podman:/mnt/shared \ podman-vm
There actually isn't an ignition file.
After I run that I can see podman-vm listed:
and can manually run
podman machine start podman-vm
:So, with this in mind, I set up a plist file to execute that command on startup:
/Library/LaunchDaemons/com.podman.vmnetd.plist
And, I thought it would work with the same user name "remove" that worked on the command line, but apparently it needs to be root. Even still, the machine doesn't start, even manually on the command line well after boot like.
sudo launchctl load /Library/LaunchDaemons/com.podman.vmnetd.plist
, and I see this in/var/log/podman/com.podman.vmnetd.err
:Does anyone know what I need to do to get this to work with LaunchDaemons? I swear, I've seen comments from people that indicate to me that this should work!
Beta Was this translation helpful? Give feedback.
All reactions