|  | @@ -209,6 +209,21 @@ Some of these will not be supported based on the settings on the host's `dockerd
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  For more information about using the experimental "rootless" image variants, see [docker-library/docker#174](https://github.com/docker-library/docker/pull/174).
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | +**Note:** just like the regular `dind` images, `--privileged` is required for Docker-in-Docker to function properly ([docker-library/docker#151](https://github.com/docker-library/docker/issues/151#issuecomment-483185972) & [docker-library/docker#281](https://github.com/docker-library/docker/issues/281#issuecomment-744766015)). For `19.03.x` rootless images, an argument of `--experimental` is required for `dockerd` ([docker/docker#40759](https://github.com/docker/docker/pull/40759)).
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +Basic example usage:
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +```console
 | 
	
		
			
				|  |  | +$ docker run -d --name some-docker --privileged docker:dind-rootless
 | 
	
		
			
				|  |  | +$ docker logs --tail=3 some-docker # to verify the daemon has finished generating TLS certificates and is listening successfully
 | 
	
		
			
				|  |  | +time="xxx" level=info msg="Daemon has completed initialization"
 | 
	
		
			
				|  |  | +time="xxx" level=info msg="API listen on /run/user/1000/docker.sock"
 | 
	
		
			
				|  |  | +time="xxx" level=info msg="API listen on [::]:2376"
 | 
	
		
			
				|  |  | +$ docker exec -it some-docker docker-entrypoint.sh sh # using "docker-entrypoint.sh" which auto-sets "DOCKER_HOST" appropriately
 | 
	
		
			
				|  |  | +/ $ docker info --format '{{ json .SecurityOptions }}'
 | 
	
		
			
				|  |  | +["name=seccomp,profile=default","name=rootless"]
 | 
	
		
			
				|  |  | +```
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  |  ## Where to Store Data
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `%%REPO%%` images to familiarize themselves with the options available, including:
 |