update for current images

Author: alexbatashev

sycl/doc/GetStartedGuide.md

@@ -46,11 +46,11 @@ and a wide range of compute accelerators such as GPU and FPGA.
   * Windows: `Visual Studio` version 15.7 preview 4 or later -
     [Download](https://visualstudio.microsoft.com/downloads/)
 
-Alternatively you can use Docker image, that has everything you need
+Alternatively, you can use Docker image, that has everything you need
 pre-installed:
 
 ```
-docker run --name sycl_build -it --entrypoint=/bin/bash -v /local/workspace/dir/:/src ghcr.io/intel/llvm/ubuntu2004_base
+docker run --name sycl_build -it -v /local/workspace/dir/:/src ghcr.io/intel/llvm/ubuntu2004_base /bin/bash
 ```
 
 This command will start a terminal session, from which you can proceed with the

sycl/doc/dev/DockerBKMs.md

@@ -5,7 +5,7 @@
 Docker and Podman are very similar tools, that allow you to manage and run
 container images. Unlike Docker, Podman runs without a daemon, allows you to run
 containers without root permissions, but does not let you build a container from
-source. The command line syntax is mostly identical for Docker and Podman.
+the source. The command line syntax is mostly identical for Docker and Podman.
 Choose whatever is available on your system.
 
 ## SYCL Containers overview
@@ -14,27 +14,27 @@ The following containers are publicly available for DPC++ compiler development:
 
 - `ghcr.io/intel/llvm/ubuntu2004_base`: contains basic environment setup for
    building DPC++ compiler from source.
-- `ghcr.io/intel/llvm/ubuntu2004_intel_drivers`: contains everything from base
-   container + pre-installed Intel drivers. This image provides two main tags:
-   `latest`, that uses latest available drivers, and `stable`, that uses
-   recommended drivers.
-- `ghcr.io/intel/llvm/ubuntu2004_nightly`: contains latest successfully built
-   nightly build of DPC++ compiler, as well as pre-installed Intel drivers.
+- `ghcr.io/intel/llvm/ubuntu2004_intel_drivers`: contains everything from the
+   base container + pre-installed Intel drivers.
+- `ghcr.io/intel/llvm/sycl_ubuntu2004_nightly`: contains the latest successfully
+   built nightly build of DPC++ compiler. The image comes in two flavors:
+   with pre-installed Intel drivers (`latest`) and without them (`no-drivers`).
 
 ## Building a Docker Container from scratch
 
-Docker containers can be build with the following command:
+Docker containers can be built with the following command:
 
 ```
 docker build -f path/to/devops/containers/file.Dockerfile path/to/devops/
 ```
 
-The `ubuntu2004_preinstalled.Dockerfile` script expects `llvm_sycl.tar.gz` file
+The `ubuntu2004_preinstalled.Dockerfile` script expects `llvm_sycl.tar.xz` file
 to be present in `devops/` directory.
 
-Containers other than base provide several configurable arguments, most commonly
-used are`base_image` and `base_tag`, that specify base Docker image and its tag.
-You can set additional arguments with `--build-arg ARG=value` argument.
+Containers other than base provide several configurable arguments, the most
+commonly used are `base_image` and `base_tag`, which specify the base Docker
+image and its tag. You can set additional arguments with `--build-arg ARG=value`
+argument.
 
 ## Running Docker container interactively
 
@@ -43,7 +43,7 @@ you to run containers interactively, so that you can use it as you would use a
 terminal or SSH session. The following command allows you to do that:
 
 ```
-docker run --name <friendly_name> -it --entrypoint /bin/bash <image_name>[:<tag>]
+docker run --name <friendly_name> -it <image_name>[:<tag>] /bin/bash
 ```
 
 This command will download an image, if it does not exist locally. If you've
@@ -53,12 +53,46 @@ downloaded an image previously, and you want to update it, use
 ## Passthrough an Intel GPU to container
 
 Add `--device=/dev/dri` argument to `run` command to passthrough you Intel GPU.
+Make sure you're a member of `video` group to be able to access GPU.
 
 ## Passthrough a directory to container
 
 Use `-v path/on/host:path/in/container` argument for `run` command to
 passthrough a host directory or a file.
 
+## Persisting data with volumes
+
+Docker container images are read-only. When container is destroyed, all its data
+is lost. To persist data when working with containers (i.e. when upgrading
+container version) one can use Docker volumes.
+
+Creating a volume:
+
+```
+docker volume create <volume name>
+```
+
+Listing all volumes:
+
+```
+docker volume list
+```
+
+Mounting volume to the container:
+
+```
+docker run <options> -v <volume_name>:/path/inside/container <image_name> bash
+```
+
+Deleting a volume:
+
+```
+docker volume rm <image_name>
+```
+
+See [official documentation](https://docs.docker.com/storage/volumes/) for more
+info.
+
 ## Managing downloaded Docker image
 
 List local images:
@@ -70,3 +104,47 @@ Remove local image:
 ```
 docker image rm <image_name_or_id>
 ```
+
+## Change location of the images on the system
+
+By default Docker stores images in `/var/lib/docker`, but that can be changed.
+
+Create a new file called `/etc/docker/daemon.json` and put the following
+content:
+
+```
+{
+  "data-root": "/path/to/data/root",
+  "exec-root": "/path/to/exec/root"
+}
+```
+
+## Running Docker without sudo
+
+Add your local user to `docker` group to be able to run docker commands without
+sudo.
+
+## Changing Docker user
+
+By default all processes inside Docker run as root. Some LLVM or Clang tests
+expect your user to be anything but root. You can change the user by specifying
+`-u <username or uid>` option. All Docker containers come with user `sycl`
+created.
+
+## Managing disk usage
+
+See how much space is taken by docker:
+
+```
+docker system df
+```
+
+Cleaning unused data:
+
+```
+docker system prune
+```
+
+See [official documentation](https://docs.docker.com/engine/reference/commandline/system_prune/)
+for more info.
+