-
Notifications
You must be signed in to change notification settings - Fork 486
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
"handle is invalid" error for volume inspection/creation but not for pod creation during a podman-compose up (On windows) #336
Comments
this might be due to having |
please make sure to use the devel
|
Hello, more news hoping that someone can help me. the problem happens also on another computer so this does not seem to be an isolated issus. And second, i discover that when I want to redirect the output of a podman command I have the same error: (and the podman --version > C:\Users\tipaty\Downloads\podman-2.2.1_tmp\test ) did not write anythong in the file but it has emptied it) |
so this is a problem of @rhatdan it seems that podman gives an error when having its output redirected on windows. |
Yes, indeed it's a problem of podman, I also noticed that when I use Popen and add stdout=subprocess.PIPE in the arguments of the function (it allows to store the stdout) I also have the "handle is invalid error". I suppose that it needs to write somewhere the output and so we have the error (here I'm juste guessing) |
I checked on the podman github annd there is an issue about it has been corrected, se we need to wait for a next release So i close the issue here. |
Hello,
I'm trying to use podman-compose on windows, I've got podman configure with minikube (so podman remote on my windows and a VM is created by Minikube to run podman), I don't have any problem with podman, everything is working perfectly.
But with podman-compose I've got an issue.
I'm learning podman so I started with the apps that were used for a pluralsight class (that worked well when I was using docker).
it starts by creating a pod, which completes succesfully, then it inspects the volumes defined in the docker-compose.yml (or create it if it does not exist), But this part fails with "handle is invalid" (I'm not totally sure what it means but as I understood it, it means my Podman is not good for execution Podman command (sry I may be totally wrong but I'm a beginner :D) ) for both inspection and creation of the volume.
I noticed that in the podman-compose.py, the creation of the pod is done by the function run of the class Podman, and for the 2 others (inspection and creation of a volume) it's done by the function output of the same class.
they both use the module subprocess, run uses Popen, and output uses check_output. So I modify the script so that the inspection of the volume is executed thanks to run and not output (so Popen instead of check_output).
And the command is successful (I managed to display the json that I have if I do the podman inspect by myself), the "podman-compose up" still finishes with error because the return of the two functions are not similar, but it looks like Popen and check_output does not execute the command the same way.
I wanted to know if someone knows why with this difference of execution and how I can avoid that.
Because I can't manage to make work podman-compose
Creation of pod:
Inspection of a volume:
def run:
def output:
I changed this line: (line 362)
to this line:
And here is the 2 different output I had:
after the modification:
the error at the end is because of the format of the return
I use this version of Podman:
podman --version
C:\Users\tipaty\Downloads\podman-2.2.1\podman.exe version 2.2.1
I don't know how to check my version of podman-compose, but I know it's not devel, I just installed with pip install podman-compose (date: 6 of september 2021)
Thanks in advance for your help.
The text was updated successfully, but these errors were encountered: