Skip to content
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

Container fails to connect to scp or sftp using default backend #4

Closed
aenima opened this issue Mar 23, 2017 · 1 comment
Closed

Container fails to connect to scp or sftp using default backend #4

aenima opened this issue Mar 23, 2017 · 1 comment

Comments

@aenima
Copy link

aenima commented Mar 23, 2017

It seems like some required module for the default scp / sftp backend used by duplicity is missing in the container. When I try to connect to some scp scheme url, I get the following:

user@host:~# docker run --rm wernight/duplicity duplicity /root scp://192.168.0.1/test 
BackendException: Could not initialize backend: No module named paramiko

In this example, a scp url is used, but the error is the same for sftp urls. Also, the host doesn't have to be available for an actual connection, because the docker image is obviously missing the required package.

@aenima aenima mentioned this issue Mar 23, 2017
@aenima
Copy link
Author

aenima commented Mar 24, 2017

After merging the bugfix, this should be working now. Closing

@aenima aenima closed this as completed Mar 24, 2017
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

No branches or pull requests

1 participant