-
|
The problem: I want to be able to run containers on different machines on the same host. For example, I created several machines with different parameters: disk size, mounted volumes, etc. I want to run one container with access to my mounted volumes and other containers without it. I would imagine an additional argument to container commands should exist, like: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
why do you need two machines to run one container with a volume and one without? one container would have a -v macos:vm and the other wouldn't |
Beta Was this translation helpful? Give feedback.
-
|
Using different volumes was just one of the examples. Let's put it this way: if I can create more than one machine to run containers in them -- I should have an easy way to tell |
Beta Was this translation helpful? Give feedback.
-
|
You set the |
Beta Was this translation helpful? Give feedback.
-
|
That works! Thanks, @Luap99! |
Beta Was this translation helpful? Give feedback.
-
|
You can also use cli arg for this. |
Beta Was this translation helpful? Give feedback.
-
|
This is what I was looking for! Somehow I couldn't find it in the docs, but now I see it in |
Beta Was this translation helpful? Give feedback.
-
|
Yes podman machine just manages the VM and sets up a connection. The rest is handled by the regular remote client which exists much longer than podman machine. https://docs.podman.io/en/latest/markdown/podman-remote.1.html |
Beta Was this translation helpful? Give feedback.
-
|
you can run like this: |
Beta Was this translation helpful? Give feedback.
You set the
CONTAINER_CONNECTIONenvironment variable, e.g.CONTAINER_CONNECTION=machine2 podman ...Or you just run
export CONTAINER_CONNECTION=machine2to set for you current session so you can use justpodman ...