-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Building and installing podman from source unavailable on macos #9032
Comments
Sounds great. Interested in opening a PR for the Makefile to work correctly by default on a MAC? |
@rhatdan I would not mind helping with that task but at this moment there is zero documentation on how someone would even manually build podman from source on a mac and this makes testing impossible. Shortly, show me some manual steps and I will automate them, or at least automate most of them. There are lots of bugs where I would be pleased to help, like #8323 but lack of build docs does not help. |
@baude @ashley-cui Could you help @ssbarnea out. |
@ssbarnea I'll document but here's the gist:
|
add instructions on how to build podman on macOS. big thanks to acui for help in getting this written down. Fixes: containers#9032 Signed-off-by: baude <[email protected]>
As I said in the other PR. It would be very nice if the Makefile realized it is on a MAC and then just made the podman-remote binary as podman automajicly and then you used make install to install it. |
At this moment there is no documentation on how someone can build podman and install it from source on macos. This is a real problem as it prevents testing of code from master or testing patches.
For example at #7806 (comment) it is mentioned a patch that merged more than month ago but which cannot really be confirmed as working or not because there is no clear documentation on how to build it from source.
Ideally building and installing from source should be same as on linux, as the makefile should detect the platform and try the different build path specific to that platform.
This approach should provide a consistent hacker/developer experience, probably even more important than documenting the process. Not only this, but this would enable easy testing on github where macos hosts are available.
The text was updated successfully, but these errors were encountered: