1. Open a new terminal to your docker container

You run the docker image as in:
~/Downloads/pcs3746-sistemas-operacionais/1$ ./run.sh
In your ubuntu, do:
docker ps, as in:
~/Downloads/pcs3746-sistemas-operacionais/1$ docker ps
CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS               NAMES
ded8427efd96        tiagoshibata/pcs3746   "/entrypoint.sh /def…"   5 hours ago         Up 5 hours                              focused_swartz

You may see that we have the docker image tiagoshibata running on a docker container with ID ded8427efd96. It running for 5 hours and it has an image name blessed by docker: focused_swartz.
Now, you may open another terminal and enter again in the docker container.
Do:
~/Downloads/pcs3746-sistemas-operacionais/1$ docker exec -ti focused_swartz bash
Note that you must insert the name given by "docker ps" and not necessarily focused_swartz.

~/Downloads/pcs3746-sistemas-operacionais/1$ docker exec -ti focused_swartz bash
root@ded8427efd96:/# 
root@ded8427efd96:/# su student
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

student@ded8427efd96:/$ ps ax
  PID TTY      STAT   TIME COMMAND
    1 pts/0    Ss+    0:00 /bin/bash /entrypoint.sh /default_cmd.sh
    7 pts/0    S+     0:00 su student -c env PATH=/usr/local/sbin:/usr/local/bin
    8 ?        Ss     0:00 /bin/bash /default_cmd.sh
 2616 ?        Sl     0:01 qemu-system-arm -M versatilepb -m 128M -nographic -ke
 2620 pts/1    Ss     0:00 bash
 2630 pts/1    S      0:00 su student
 2631 pts/1    S+     0:00 bash
 2640 pts/2    Ss     0:00 bash
 2650 pts/2    S      0:00 su student
 2651 pts/2    S      0:00 bash
 2658 pts/2    S+     0:00 arm-none-eabi-gdb -ex target remote:1234 /home/studen
 2666 pts/3    Ss     0:00 bash
 2675 pts/3    S      0:00 su student
 2676 pts/3    S      0:00 bash
 2682 pts/3    R+     0:00 ps ax
student@ded8427efd96:/$ 

Now you may see all the processes running on the ubuntu inside your docker image, specially, you may see qemu-system-arm.
That is it! You may create as many terminals to your docker container (an instance of your docker image) as you want.
In the next post, I will show how this new terminal may connect to qemu via gdb.





Comentários

Postar um comentário

Postagens mais visitadas deste blog

Basics on ARM processor

Imagem
I am also teaching "Laboratory of Microprocessors" focusing ARM. I use  ARM Lab Manual  for the first experiences.  I have been asking students to install a tool chain in ubuntu to develop experiments in the simulator provided by arm-...-gdb. Last year, one team made everything as the docker image: https://github.com/EpicEric/gcc-arm.git In order to use it:  git clone https://github.com/EpicEric/gcc-arm.git See README.md  cd gcc-arm/ ./build_docker.sh emacs # any other editor that you prefer; perhaps, you will need sudo,and perhaps gedit suchs as:                sudo ./build_docker.sh gedit docker run --rm -ti -v "$PWD/src":/home/student/src epiceric/gcc-arm Note that your directory $PWD/src is attached to /home/student/src. In this docker image, we have 2 tool-chains: arm-elf and arm-none-eabi. In the first part of the course, we are using arm-elf. We will use arm-none-eabi to deal with ...
Leia mais

Arm Linux Kernel on docker image with qemu and tool chains - building

I am used to ask for 4 to 5 assignments in the Operating Systems course - PCS3746. Last year, it was four. My former student Tiago Shibata put the work of his team on: https://github.com/tiagoshibata/pcs3746-sistemas-operacionais He did not provide much documentation. I will do it. This links points to the source code necessary to build a docker image. A docker image is some kind of light virtual machine where you insert everything you need and nothing more. In a normal virtual machine, you would install ubuntu with X windows, Unity, and a lot of stuff that is not related to what we want: an ARM Linux kernel. Besides, a normal virtual machine, it emulates the hardware, I/O (clock, hard disk, etc.), BIOS, etc. while a docker image makes use of the Linux system calls. So, a docker image consumes much less resource than a real virtual machine. In order to run a docker image, you can: download the image and run it. download the image source, build and run it. As I will ask to m...
Leia mais

2. run gdb

So far you must have two terminals on your docker container: One that shows the output of qemu ... -s -S One that is in a bash. See that you can give commands such as: ls, cd, etc.  You see something like this: $ docker exec -ti upbeat_khorana bash root@db40c62a2c8d:/# su student To run a command as administrator (user "root"), use "sudo <command>". See "man sudo_root" for details. student@db40c62a2c8d:/$ alias alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"' alias egrep='egrep --color=auto' alias fgrep='fgrep --color=auto' alias gdb='arm-none-eabi-gdb -ex '\''target remote:1234'\'' /home/student/src/linux/vmlinux' alias grep='grep --color=auto' alias l='ls -CF' alias la='ls ...
Leia mais