...
On a Macbook pro (M1) the build of OpenIFS, takes about 10 minutes, while successful completion of ifstest takes just over 3 minutes.
Notes about containers
Exiting the container
...
Check existing containers
From
...
a terminal on the host system
...
,
...
it is
...
- Push any code changes back to a repo
- If data is required either set-up a data volume or copy the data back to a local machine, using
docker cp
Check for existing containers, stopping, restarting
Executing docker run will always create a new container, which will be retained if the run command does not include the --rm. This is not ideal and so here are some commands to manage the containerspossible to list running and exited containers with the following
List running containers
Code Block language bash theme Midnight docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d1bd89ccc47f openifs-48r1.1 "bash" 15 hours ago Up 5 seconds beautiful_pasteur
If no container is running on your system, then only CAPITAL headings are returned with
docker psList all containers (running and exited)
Code Block language bash theme Midnight docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d1bd89ccc47f openifs-48r1.1 "bash" 15 hours ago Exited (0) 4 seconds ago beautiful_pasteur
Notice that the
STATUSisExited, rather thanUp, as in (1)
Start an existing container
Executing docker run will always create a new container, which will be retained if the run command does not include the --rm. If a container is not removed when exited, then it can be restarted
Exiting the container
- The container can be exited by typing
exitfrom the active container. - A container can be stopped from a terminal on the host system
- Once exited all data and changes made within the container will be lost. Hence, if necessary, it is important to
- Push any code changes back to a repo
- If data is required either set-up a data volume or copy the data back to a local machine, using
docker cp
- Start an existing container
...