Platform For AI:Use Docker in DSW

Start a secondary container

Run the following command to start and enter a secondary container:

docker run -it dsw-registry.cn-hangzhou.cr.aliyuncs.com/pai/pytorch:1.8PAI-gpu-py36-cu101-ubuntu18.04 /bin/bash

Mount devices to a secondary container

• GPUs — Use --gpus=all to mount all GPU devices of the DSW instance.

• PPUs — Unlike GPUs, PPU devices must be manually mounted to the secondary container by using the --device parameter:

docker run -it --network=host \
  --device=/dev/alixpu_ppu0 \
  --device=/dev/alixpu \
  --device=/dev/alixpu_ctl \
  your-ppu-enabled-image

Mount data to a secondary container

Use Docker Bind Mount to access data in a secondary container. Mount the data to the DSW instance by using Dataset Mounting or Storage Path Mounting, and then mount it to the secondary container. Volume Mount and tmpfs Mount are not supported.

For example, if the DSW instance has data mounted at /mnt/data0 and /mnt/data1, use the -v parameter or the --mount parameter to bind mount the data to the secondary container:

# In this example, <path_in_dsw> can be /mnt/data0, /mnt/data1, or their subpaths.
# Other paths cannot be mounted to the secondary container for now.

# Use the -v parameter
docker run -v <path_in_dsw>:<path_in_secondary_container>[:options] {image}

# Use the --mount parameter
docker run  --mount type=bind,source=<path_in_dsw>,target=<path_in_secondary_container>[,readonly] {image}

Access a secondary container

Use the docker exec command to start a new command process in a running container.

For example, to start a bash shell in interactive mode with standard input open (-i) and a pseudo-terminal allocated (-t), run the following command:

docker exec -it your-container /bin/bash

You can also use the docker attach command to attach to the terminal of the main process in a running container. If you started the container with standard input open (-i) and a pseudo-terminal allocated (-t), you can view and interact with the standard input and output (stdin/stdout/stderr) of the container:

docker attach {container_id}

Q: Why are the processes of secondary containers not visible when I run the ps -aux command in a DSW instance?

The main container and secondary containers in a DSW instance do not share a PID namespace. Therefore, the processes of secondary containers are not visible from the main container.

Q: Why does pulling an image from Docker Hub fail?

Due to network restrictions, pulling images directly from Docker Hub fails. You receive the following error:

root@dsw-381955:/mnt/workspace# docker run --network=host -it ubuntu /bin/bash
Unable to find image 'ubuntu:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded.
See 'docker run --help'.

Instead, pull images from the Artifact Center of Alibaba Cloud Container Registry (ACR). For instructions, see Pull images. Alternatively, see Cross-domain pull of overseas models or container images.

Q: What do I do if I receive the error "Error response from daemon: authorization denied by plugin authZ: Permission denied"?

You used a Docker command or parameter that is not supported. If you have questions, submit a ticket to contact technical support.

Q: What do I do if I receive the error "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

Check whether the /var/docker/proxy/docker-proxy.sock file exists in the DSW instance. If the file exists, run the following command:

export DOCKER_HOST=unix:///var/docker/proxy/docker-proxy.sock

Then, run the Docker command again.