Docker container still downloading and executing even after a complete delete

docker system prune -a will remove all unused images , so assuming that you when executing this command - it is possible that tutum/apache-php image was used by the running-container and it was not created/started by the current docker-compose.yml file (may be docker-compose.yml file had this entry before).

docker@default:~$ docker system prune --helpUsage:  docker system prune [OPTIONS]Remove unused dataOptions:  -a, --all             Remove all unused images not just dangling ones      --filter filter   Provide filter values (e.g. 'label=<key>=<value>')  -f, --force           Do not prompt for confirmation      --volumes         Prune volumesdocker@default:~$

Can you stop the container (use container-id or name) and remove it,
just to ensure if tutum/apache-php container was created+started again when you invoke docker-compose up ?

#>docker rm -f 3807234b989f        #>docker rm -f 551acc487c9d        #>docker system prune -a#>docker-compose up#>docker-compose ps#>docker ps

Let me know if you get the same output as you were getting earlier.