https://open-source-silicon.dev logo
Join Slack
Powered by
Hi, I was able to get klive and do all of is in th...
# ieee-sscs-dc-24
f
Hi, I was able to get klive and do all of is in the Environmet Setup document. However, when I run the python script to test. I find this in my terminal saying Klive isn't present even though I installed it?
s
Do you klayout open in a separate window
In order to connect to klive you have top have it open in a separate window
f
I do not.
s
Try that
f
1. How can I enter and inout the installation check steps within 
root@ID:
. I run 
docker run -it -v /tmp/.X11-unix:/tmp/.X11-unix -v /mnt/wslg:/mnt/wslg -v $(pwd):$(pwd) -w $(pwd)  -e DISPLAY -e WAYLAND_DISPLAY -e XDG_RUNTIME_DIR -e PULSE_SERVER --name glayoutcontainer openfasoc:glayout
But face the following message: 
docker: Error response from daemon: Conflict. The container name "/glayoutcontainer" is already in use by container "295ff9370d3a6ca6411aacfd159ddefebb659b6c8d0aaa5935c7cc297d9219cf". You have to remove (or rename) that container to be able to reuse that name.
s
give it another name like glayoutcontainer1
--name glayoutcontainer1
f
And I opened another window to host the live with 
xhost +Local:*
s
or you can remove the container: docker rm glayoutcontainer
f
For my understanding, what is the purpose of creating a new container rather than remaining within the old container? Does the new container inherit what was done in the old container?
s
You could use that approach. but when you reuse a container by using 
exec
you can't mount volumes
-v $(pwd):$(pwd)
gives the container access to your working directory
Its only available with 
run
When you build a docker file, you create an image (think of it as a system suspended in time with certain packaged installed). When you run using 
run
you make a copy of that image so you can run commands on it. When you run again using 
run
you make another copy of the image (not of the container you run previously).
That's why for the klive installation I used the 
commit
command, because that creates an image of the container you installed klive on, and if you were to run another container with the original image you would not have access to klive.
f
It is done! Thank you so much for your responses and assistance!
🥳 1
r
@Sakib Pathen Speaking of which, does it mean that we always have to create an image based on the current container by running "docker commit containerID image-name:tag" before exiting the container so that we can use it again when we create another new container?
s
No, all you need is an image to run glayout scripts and klayout
3 Views
Open in Slack
PreviousNext
Powered by