Hi all, I am following the steps on this <video>. ...
# ieee-sscs-dc-24
f
Hi all, I am following the steps on this

video

. I, however, am facing an issue when attempting to run the following command: " sudo docker build -t openfasoc:glayout . ". I am running WSL. Any help is appreciated!
I see this error.
s
Did you follow the steps to install docker
Run these commands: sudo apt-get update sudo apt-get install ca-certificates curl sudo install -m 0755 -d /etc/apt/keyrings sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc sudo chmod a+r /etc/apt/keyrings/docker.asc # Add the repository to Apt sources: echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update And then after run this command
Sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
f
I ran the first set of commands, but not the latter. Is it okay to simply run the last command without redoing the first set?
s
Yes, it is okay
f
Download complete. Thank you. New message appears
I run this test but the same message appears.
s
Try
Copy code
systemctl start docker
f
I recieve the following.
System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down.
So sorry with all these issues!
s
Wow, this is very wierd, this is in Ubuntu in WSL?
Are you running this within the container?
f
This is my configuration
Openfasoc? Yes
v
while my docker was successfully installed, I got stuck with many issues (few of the above mentioned too) with the installation on WSL... even after following all the steps exactly as in the document going to do a fresh install later.
s
Can you try the conmand "sudo service docker start" and let me know how that goes?
f
This is good, no?
s
Yes, now run the build command
f
hmm, same message as before
message has been deleted
s
Can you show me the output of
Copy code
sudo service docker status
f
message has been deleted
s
Maybe restart the WSL instance when run service docker start and service docker status again?
If it says that its running then try building again, if it doesnt work then try this:
f
Restarting WSL as closing the window and opening a new one?
s
Copy code
sudo update-alternatives --config iptables # enter 1 to select iptables-legacy
sudo service docker start
sudo service docker status
To restart use the command
Copy code
wsl --shutdown
And then start the instance like you did previously
f
I face this.
s
Type 1 and pres enter
f
Good news! the docker is building!
s
Nice! I will add this to the installation document in case someone else is encountering this issue
@Vaibhav Singh can you try replicating this and see if that fixes your issue?
f
I will continue the steps on the video. Thank you so so much!
👍 1
v
untill step 6 this is the status, after this should I restart the WSL or continue with the commands mentioned in step 7 and 8
this is the result after step 7
s
keep proceeding
v
didnt't restart, continued with the 8th step, 7th step in different terminal window
going through the above thread, I installed Docker successfully previously and tested the hello world command message, it worked well, should I follow the same steps, as Freddy also faced the same issue
s
dont run a docker container within the docker container
the run command is meant to be run within wsl
the high level view of the steps are these: 1. on your wsl machine, install docker 2. build the docker image provided in the openfasoc repository 3. once its built, run the command to run the container within WSL
v
so the root@(numeral) is already a docker container, so I should directly run the commands in step 9, and at other times while opening a new terminal in wsl step 8, to open the container I built ?
s
yes
v
is this correct ?
s
Yes, if this is after running test_glayout.py
Have you tried opening klayout
v
yes this was after test_glayout.py
not tried opening klayout, for that I have to follow the steps in the video or Next: Coding with GLayout in the documentation?
s
try running klayout within the container
just type
Copy code
klayout
v
sorry but...
s
did you try xhost +Local:* on your WSL machine?
v
yes
xhost +Local:*
Command 'xhost' not found, but can be installed with:
sudo apt install x11-xserver-utils
vaibhavpc@brutus:~$ sudo apt install x11-xserver-utils
vaibhavpc@brutus:~$ xhost +Local:*
non-network local connections being added to access control list
did xhost +Local:* again, tried to open klayout in the container, same error as before
everytime if I start my WSL, I have to docker rm-<container id> of the latest one and run, or I am missing out the commands to open the existing one?
k
Are you exiting the container the right way ? It can happen if you don't quit the container properly
v
how one can do that ? I just
exit
or I dont exit one, how one can go into the running container?
c
if the container is running do this
sudo docker exec -it glayoutcontainer bash
if it is stopped run
sudo docker container restart glayoutcontainer
you can't go into another container when you're already in a container, its not recommended at least