https://open-source-silicon.dev logo
Join Slack
Powered by
Hi, does any one have or know how to solve this is...
# ieee-sscs-dc-24
s
Hi, does any one have or know how to solve this issue? I followed the instructions and tried running klayout, but even after using "xhost +Local:*", I get the same error. I am using Windows 11 with wsl and Docker.
c
can you send the command you ran the container with
try these commands instead 
xhost +local:docker
and 
sudo docker run -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=${DISPLAY} -v $(pwd):$(pwd) -w $(pwd) --network host --name {container_nam_here} -it {image_name_her}
s
That made the trick. Thanks!
To keep a log. Instead of the second command, I executed 
sudo docker run -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=${DISPLAY} -v $(pwd):$(pwd) -w $(pwd) --network host -it openfasoc:glayout
. Due to I already had a container running under the name of 
glayoutcontainer
.
My bad. My edit of the command creates a different container after each execution. Which I noticed after seeing multiple instances in the docker app. Eitherway, if you are using the docker desktop app in windows, you can run the container with the run button and then in your ubuntu terminal you can use 
sudo docker ps
to check all the running containers, and then use 
sudo docker exec -it {my_container_name} /bin/bash
to access it.
c
if you want to run a container once you can use this
Copy code
sudo docker run --rm -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=${DISPLAY} -v $(pwd):$(pwd) -w $(pwd) --network host -it {image_name_her}
the 
--rm
flag deletes the container on exit
s
mmm I see. I was getting mixed up. My goal was to have a persistent container, but now I understand. Thank you
4 Views
Open in Slack
PreviousNext
Powered by