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
Apparently the following code
detects "Microsoft" in /proc/version and assumes it can access clip.exe.
However, that is not the cas in the docker container running under docker on a windows machine. The docker container has a virtual display itself and provides the clipboard.
/etc/resolv.conf:# Generated by Docker Engine.
/etc/resolv.conf:# This file can be edited; Docker Engine will not make further changes once it
/proc/mounts:overlay / overlay rw,relatime,lowerdir=/var/lib/docker
/usr/local/bin/docker-entrypoint.sh:
The text was updated successfully, but these errors were encountered:
Apparently the following code
detects "Microsoft" in /proc/version and assumes it can access clip.exe.
However, that is not the cas in the docker container running under docker on a windows machine. The docker container has a virtual display itself and provides the clipboard.
So I think the detection needs to be fine-tuned.
pyperclip/tests/test_pyperclip.py
Lines 119 to 123 in e16fa9c
The goal of docker is to not give away that the application is running in docker and they suggest to set a variable.
However I found:
The text was updated successfully, but these errors were encountered: