You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Aider in Docker the various options to copy to and from the clipboard do not work.
First of all Pyperclip can't find a way to access the clipboard inside the container. One major thing that is missing here is that xclip is not installed in the container image, and that clipboards aren't shared with containers by default (to my knowledge).
Another major issue is that Pyperclip doesn't play nice with Wayland, which is the gold standard in ubuntu today. That might be for a different issue though, as it's likely just as much of an issue when running aider in a non-docker installation. But still.. :-)
There are ways around this, for example to create a wrapper script inside the container named "xclip" and then mapping the relevant Wayland socket into the container, something like this: docker -v /run/user/1000/wayland-0:/run/user/1000/wayland-0
There's more to do than just the above. The main point is that there are gaps here that aren't easily solved by end users who want to run Aider in a docker container as described on the aider home page. The description needs to be expanded to include workarounds, or to include a note stating that this specific functionality isn't available when running in Docker.
Version and model info
No response
The text was updated successfully, but these errors were encountered:
Issue
When running Aider in Docker the various options to copy to and from the clipboard do not work.
First of all Pyperclip can't find a way to access the clipboard inside the container. One major thing that is missing here is that xclip is not installed in the container image, and that clipboards aren't shared with containers by default (to my knowledge).
Another major issue is that Pyperclip doesn't play nice with Wayland, which is the gold standard in ubuntu today. That might be for a different issue though, as it's likely just as much of an issue when running aider in a non-docker installation. But still.. :-)
There are ways around this, for example to create a wrapper script inside the container named "xclip" and then mapping the relevant Wayland socket into the container, something like this:
docker -v /run/user/1000/wayland-0:/run/user/1000/wayland-0
There's more to do than just the above. The main point is that there are gaps here that aren't easily solved by end users who want to run Aider in a docker container as described on the aider home page. The description needs to be expanded to include workarounds, or to include a note stating that this specific functionality isn't available when running in Docker.
Version and model info
No response
The text was updated successfully, but these errors were encountered: