[WIP] Container Providers and other fixes #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Discovery of alternative local container providers
NOTE: in the current state this is just a proof of concept to unblock me on a project, If I can get the go ahead to complete the implementation I will update this PR with the full implementation and remove this note, see todo section.
Motivation
podman
on my development machine, and its api is mostly compatible with dockerpodman
Other changes
I discovered the
image
name does not includelocalhost/
before it when loaded into the vps, this may be apodman
specific issue or its simply a bug. Since Sidekick does not support registry (that i know of), i think it makes sense to have images loaded withlocalhost/<imageName>
TODO
podman
as a remote container provider (on the VPS)Testing
Tested with a simple python app and my proxmox server running a VM