31–40 of 62 posts
MIT 6.S094 has a Dockerfile[^1] that contains all the software required for taking part in the class. This is a huge boon for getting stuck into the class and its coursework.
Prune seems not that well thought to me. Don't get me wrong, I do find it useful but many people use containers as environments. Think about how many people are going to run prune only to find their work go missing. If you are gonna add a nuclear button, do it with a big red alert and give the option to whitelist some containers.
Would have seemed more intuitive to me.
I'm just a guy that wants to deploy web apps. Is docker overkill for me? Basically, I want to be able to test something on my local machine under the same conditions it will be running on my server. Containerisation seems like the only way to do this that doesn't involve keeping packages and system configurations in sync in two or more systems.
> Containerisation seems like the only way to do this that doesn't involve keeping packages and system configurations in sync in two or more systems. Virtual machines will also work. Docker serves as a lightweight virtualization that will provide the same experience, assuming you are willing to keep to the kernel and Docker version "in sync" between prod and local.
I'm really looking forward to seeing the scientific community adopt docker as a way to distribute reproducible research and coursework. MIT 6.S094 has a Dockerfile[^1] that contains all the software required for taking part in the class. This is a huge boon for getting stuck into the class and its coursework. [^1]: http://selfdrivingcars.mit.edu/files/Dockerfile
There's been some effort individually to integrate Docker with Condor (after all, both are just processes running on some host machine).
Why not one 'prune' command with 'containers', 'images', ... as an argument / subcommand? Would have seemed more intuitive to me.
Earlier quoted context omitted.
I have a gist for it: https://gist.github.com/pubkey/73dcb894cf5f7d262863 #stop and delete all containers docker rm -f $(docker ps -a -q) #delete all images docker rmi -f $(docker images -q)
This is NOT equivalent. The OP was talking about removing unused images. Your commands remove all images.
docker rm $(docker ps -qa --no-trunc --filter "status=exited")
docker rmi $(docker images --filter "dangling=true" -q --no-trunc)I'm just a guy that wants to deploy web apps. Is docker overkill for me? Basically, I want to be able to test something on my local machine under the same conditions it will be running on my server. Containerisation seems like the only way to do this that doesn't involve keeping packages and system configurations in sync in two or more systems.
Prune seems not that well thought to me. Don't get me wrong, I do find it useful but many people use containers as environments. Think about how many people are going to run prune only to find their work go missing. If you are gonna add a nuclear button, do it with a big red alert and give the option to whitelist some containers.
That's kind of like saying the 'rm' command is not well thought out, because many people wouldn't want to delete the whole file system when running 'rm -r /'.
Also, when ran in bash but also supported by other shells, it supports regular expressions and extended pattern matching letting you for example specify not which files you want deleted, but which files you want not.