Open florentulve opened 1 year ago
ShutdownRepo
commented
1 year ago Would you be able to do the change on your end and open a PR? As it is not our priority to support podman we won't spend time on it for the time being, but if there are pull requests that bring those changes we will be more than happy to review 🫡
florentulve
commented
1 year ago Ok, that's fair. I've made some other fixes to make things work. I'll open a pr when I will have enough time to to wrap it up.
ShutdownRepo
commented
1 year ago It'd be awesome! Thank you
xAiluros
commented
12 months ago @florentulve do you happen to have anything you can share w.r.t. the mentioned fixes? Even if just poc or not fully working, it would be appreciated
florentulve
commented
11 months ago @florentulve do you happen to have anything you can share w.r.t. the mentioned fixes? Even if just poc or not fully working, it would be appreciated
@xAiluros , made a small PR with the fixes I have done so far.
xAiluros
commented
11 months ago @florentulve do you happen to have anything you can share w.r.t. the mentioned fixes? Even if just poc or not fully working, it would be appreciated
@xAiluros , made a small PR with the fixes I have done so far.
Thank you! Hope I can try it out soon and will try to see if I can improve anything
Describe the bug
The wrapper is able to download and installed an image correctly. However, further exegol install invocation does not report installed image.
After some debugging and step by step execution, i'v found that podman include the registry in the image tag, docker may not do it by default when docker.io registry is involved.
Steps To Reproduce
No response
Exegol Wrapper Version
Host OS
None
Configuration of the concerned container
No response
Execution logs in debug mode
Exception
No response
Anything else?
No response