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

Error due to HOME env inside container / interaction with tramp-histfile-override #26

Open
GPPassos opened this issue Aug 12, 2019 · 0 comments

Comments

@GPPassos
Copy link

Hi,

I noticed a problem due to interaction of docker-tramp with the variable tramp-histfile-override.
The default value for this variable is ~/.tramp_history.
However, this is troublesome for when the environment variable HOME inside the container has some kind of problem (for instance, it is empty, or it refers to a non-existing directory, which may happen to some containers).

The problem is that, when trying to connect to a container in which this is the case, the connection simply fails, and there is no clear error message that it is due to that.
(I found out increasing the debug level of tramp-verbose, but of course until I found out this variable was a thing, and that it refers to a file inside the container and not in my machine...)

I am not really sure if there is any thing possible (or convenient) to solve this problem in docker-tramp, but I think it would be really useful if on the README or something similar it could be reminded to the user that the value of tramp-histfile-override should be accessible in the container. 😃

What do you think?

Thank you for your work, this is a really useful package to me.

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