Add podman-env command to allow access to the VM container runtime
#961
Comments
I would think that that part will be done already by SNC.
Same as |
I can not answer this, so asking for feedback. Nothing needed for us externally to activate? No check of enabled service or starting a systemd unit? just socket activated? |
As described here by @praveenkumar, in the VM, we need to:
First one needs to be done once and we can do that as part of SNC (I think we discussed that in f2f already). The second one I actually need to check how to enable by default on startup but I'm sure it's possible. |
|
Actually, it seems @praveenkumar already handled:
crc-org/snc@78aa9f8 . Marking that part as done. |
|
Just to be certain, I tested against the latest 4.3.0 bundle and Note however that it failed the first time with a |
|
For binaries, we'll need to use OS-specific method:
One tiny issue is the binary name difference between Linux and others, |
|
@zeenix I think we should ourself embed the podman-remote binary with CRC and extract it in |
|
Right, we do not want to depend on external package-managers. We need to
embed our version as that is the only version that can be tested
with/against.
…On Mon, Feb 10, 2020 at 6:57 PM Praveen Kumar ***@***.***> wrote:
@zeenix <https://github.com/zeenix> I think we should ourself embed the
podman-remote binary with CRC and extract it in ~/.crc/bin like we are
doing for oc bits. How to get the bits with latest master is listed
https://github.com/containers/libpod#library-and-tool-for-running-oci-based-containers-in-pods
here but I would like to get the link which have bits for release side
https://github.com/containers/libpod/releases/tag/v1.8.0 so I can get
podman-remote v1.8.0 or v1.6.4 whichever version we have in our VM. May be
@mheon <https://github.com/mheon> or @rhatdan <https://github.com/rhatdan>
might help us to provide those urls.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#961>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAOZXNHQ64PYOS2LOYXWDRCEXIZANCNFSM4KL3QBAA>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
|
If it's available in rhel/fedora, I'd prefer we use that version, same as what we do for virsh for example. |
|
Podman-remote, for linux, should probably be provided by the distribution. |
can we guarantee the version provided by the OS/distro is usable? Besides, according to schedule and planning we target macOS (and later Windows). At the moment Linux is not considered. it is easier for those people to set up a local environment anyway. We will add support, but at a later stage => while |
|
Well, one issue would be people using an older CRC, would be avoided if the user was able to install a newer version on the MAC or windows box. But getting the tools onto Windows and potentially MAC has proven difficult. The Podman team should hopefully guarantee that the podman-remote is compatible, but we are fairly young with this support. Providing a known good version for MAC and WIndows from the VM sounds like a good idea to me, but should not prevent the user from using a newer version of podman built for the host. |
this is why we extract/refer to the the |
|
@dustymabe @dgilbery In reference to #453 and coreos/fedora-coreos-tracker#231 please have a look at this issue. We have since included the components for |
|
For minikube we are using But boot2podman still allows both methods, and both of them work... |
we are also not allowing the direct root access but using |
Add subcommand to setup environment variables to use `podman-remote` with the CRC VM. Fixes crc-org#961.
Add subcommand to setup environment variables to use `podman-remote` with the CRC VM. Fixes crc-org#961.
|
@jwhonce PTAL |
|
@gbraad I looked at your code and downloaded the msi vs zip files, and found that the podman.exe's don't match. I'll get with the guys who set this up and see what has changed. Sorry for inconvenience. |
|
@jwhonce Thanks. Would be great if this can be resolved soon. We will have a release soon and would like to include all of this. We have a code-freeze this Friday and last image/embed builds will happen on Monday. Also, why is the latest a lower release than what is currently used in the RHCOS images? |
|
I have been looking into an alternative strategy by using the
While this works there are however some issues with this approach
While possible, we would like this avoid this ... |
|
The I still see the same error? The environment variables are picked up correct, as you can see this from the following snippet from the |
|
@Edward5hen ^^^ WDYT? Is there a regression in the Windows client or am I missing something? This same setup works for macOS and Linux. |
|
Against a Fedora 30 VM: so the executable is correct ... will verify again as this could have been issue with the socket activation? |
|
Still the same results: Full re-run: In the VM In the VM we have: |
|
On windows i get the same behavior as mentioned in #961 (comment). But works on macOS |
Add subcommand to setup environment variables to use `podman-remote` with the CRC VM. Fixes #961.
|
@jwhonce @rhatdan I created #1083 to follow-up on the archive and containers/podman#5440 to handle the Windows support. |
|
@gbraad Great thanks. |
|
how do I reproduce what you are doing ? |
|
I think i know what might be wrong but will need to confirm with you live so you can test on your systems. |
|
I will also create an issue to discuss the difference between the msi and zip as pointed out by @jwhonce in #961 (comment) |
|
Here's the issue about the client archive on Windows: containers/podman#5477 ^^^ |
As described in the #874 it is possible to re-use the VM to run containers from podman. This task will add the needed commands to crc, such as:
podman-envpodman-remotebinaryThe text was updated successfully, but these errors were encountered: