kubernetes/minikube

Podman Desktop driver on Mac or Win (and Linux)

Open

#8,003 opened on May 4, 2020

View on GitHub
 (18 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
co/podman-driverhelp wantedkind/documentationkind/featurelifecycle/frozenos/macosos/windowspriority/backlog

Description

We should test (and document) running the podman driver remotely, on non-Linux platforms.

Basically these platforms install podman-remote as podman, and run commands over varlink.

There is no documentation on how to set up the remote VM for Mac or Win, unfortunately...

The upstream install docs all assume that such a Linux host is already available over SSH:

https://podman.io/getting-started/installation

MacOS Podman is a tool for running Linux containers. You can do this from a MacOS desktop as long as you have access to a linux box either running inside of a VM on the host, or available via the network. You need to install the remote client and then setup ssh connection information in the podman-remote.conf file.

Windows Podman is a tool for running Linux containers. You can do this from a Windows desktop as long as you have access to a linux box either running inside of a VM on the host, or available via the network. You need to install the remote client and then setup ssh connection information in the podman-remote.conf file.

https://github.com/containers/libpod/blob/master/docs/source/markdown/podman-remote.conf.5.md

Theoretically using podman-machine should work, as long as you use the systemd one:

https://boot2podman.github.io/2018/12/07/fedora-iso-variant.html

It is also possible to do it yourself, using the hypervisor of your choice... (and a Fedora ISO)

There is a walkthrough here: https://itnext.io/podman-and-skopeo-on-macos-1b3b9cf21e60

We need to document some minikube-specific configuration, like switching over to cgroupfs

Contributor guide

Tech stack
go
Domain
devopsinfrastructuredocumentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Minikube basicsPodman remote clientVM setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the podman remote setup on macOS and Windows as described in the issue. Look at the linked podman installation docs and the podman remote.conf man page. Test the boot2podman Fedora ISO approach and document the steps for minikube users. Update the minikube documentation to include specific configuration like switching to cgroupfs.