Skip to content

feat: add incus/LXC connector #1368

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

Open
wants to merge 2 commits into
base: 3.x
Choose a base branch
from

Conversation

romain-dartigues
Copy link
Contributor

Dear pyinfra,

I started adding a LinuxContainers / Incus connector.
It is much a work in progress and I would appreciate feedback.

Actually it can:

  • work with local or remote incus/lxc server
  • execute action on all instances of the targeted incus/lxc server

It relies on the agent to be running on the targeted instance, when not the case it won't be able to do much more than getting it's name from the list and it's IPv4 address if there is one.

Examples:

# on remote servers:
pyinfra @incus/incus.example.net:instance_name files.get src=/tmp/n.log dest=n.log

pyinfra --debug -vvv --dry @incus/incus.example.net: fact server.LinuxName

# same, but target the local server
pyinfra @incus/instance_name files.get src=/tmp/n.log dest=n.log
pyinfra --debug -vvv --dry @incus/ fact server.LinuxName

@romain-dartigues romain-dartigues force-pushed the rdartigues/connectors branch 2 times, most recently from 1b406fc to c588555 Compare June 3, 2025 18:02
@romain-dartigues
Copy link
Contributor Author

Obviously I did my code without looking around...
Refs: #677, #1282

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant