Docker...
-
Docker doesn't provide VM services. Docker is not cross-platform. Docker is NOT faster/easier than writing a proper installer. Docker is just a bigger, uglier, more complex wrapper around an existing process, and it only exists because someone wanted to use a whale icon.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013John Simmons / outlaw programmer wrote:
someone wanted to use a whale icon.
Or maybe it is a hidden message to us mortals, what Docker is? :-D (with all that spirit about Docker, you may write an ant-Docker article and post it as part of the competition)
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
-
John Simmons / outlaw programmer wrote:
someone wanted to use a whale icon.
Or maybe it is a hidden message to us mortals, what Docker is? :-D (with all that spirit about Docker, you may write an ant-Docker article and post it as part of the competition)
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
I have yet to find a decent explanation as to why it exists, but it's mere existence is enough to cause me to cast a wary eye on it, not to mention create and maintain a healthy dislike of the product.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
It needs Windows 10 Pro. I did ask the guy (forgot his name) who wrote the introductory article to add this information, but never got an acknowledgement of my message.
There are several solution to run Docker... The new one (Docker for Windows) needs Windows 10 or 2016 (it is actually built in since 14393)... However there is the Docker Toolbox (older) that can go for older Windows (back to 7)
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
I have yet to find a decent explanation as to why it exists, but it's mere existence is enough to cause me to cast a wary eye on it, not to mention create and maintain a healthy dislike of the product.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I do not dislike the product, but the way it was glorified way beyond its value. And that created a hype of misunderstanding, that made our (developers) life more miserable...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
It needs Windows 10 Pro. I did ask the guy (forgot his name) who wrote the introductory article to add this information, but never got an acknowledgement of my message.
Getting Started With Docker[^] This? You right - the version the article points to, needs 10 and Pro and 64 and VT...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
I have yet to find a decent explanation as to why it exists, but it's mere existence is enough to cause me to cast a wary eye on it, not to mention create and maintain a healthy dislike of the product.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I've been amazed at the hype around and promotion of Docker, and despite friends of mine being enthusiastic about it (whilst not, it appears, actually using it) I haven't been able to think of a single use case for the environments I work in that isn't already covered by existing VM products. EG: One environment I'm developing for is already running virtualised servers, so what do I gain by taking the processes I'm currently running on one of those ( a web-app based front end to a MS-SQL back end, built with web2py/Bootstrap etc ) and putting them in another - albeit light - layer of virtualisation. Given that I cannot then run my IDE in that container, I still need to maintain a host machine to allow me to work on the code. It's not clear that a Docker instance can easily communicate with MS-SQL running elsewhere. I keep thinking I must be missing something - can anyone tell me what it is, because I can't see any gains in that environment from using Docker. Other stuff I work on requires physical access to devices...
-
I've been amazed at the hype around and promotion of Docker, and despite friends of mine being enthusiastic about it (whilst not, it appears, actually using it) I haven't been able to think of a single use case for the environments I work in that isn't already covered by existing VM products. EG: One environment I'm developing for is already running virtualised servers, so what do I gain by taking the processes I'm currently running on one of those ( a web-app based front end to a MS-SQL back end, built with web2py/Bootstrap etc ) and putting them in another - albeit light - layer of virtualisation. Given that I cannot then run my IDE in that container, I still need to maintain a host machine to allow me to work on the code. It's not clear that a Docker instance can easily communicate with MS-SQL running elsewhere. I keep thinking I must be missing something - can anyone tell me what it is, because I can't see any gains in that environment from using Docker. Other stuff I work on requires physical access to devices...
Given that I cannot then run my IDE in that container
Why is that? My team works in a Docker environment, and we all run an IDE. When a new guy arrives in the team, he just runs a "docker pull" from our registry and he's up and running with everything installed in a matter of minutes. Docker has clearly been overhyped, and we all lived our daily lives without it, but I see a lot of developers who don't make an effort to understand what it is, and most importantly what it is not, and then call it garbage.
-
Given that I cannot then run my IDE in that container
Why is that? My team works in a Docker environment, and we all run an IDE. When a new guy arrives in the team, he just runs a "docker pull" from our registry and he's up and running with everything installed in a matter of minutes. Docker has clearly been overhyped, and we all lived our daily lives without it, but I see a lot of developers who don't make an effort to understand what it is, and most importantly what it is not, and then call it garbage.
Interesting - espcially given the convoluted explanation I read hereabouts of how to get Netbeans to work in a docker container! I'm no expert on Docker I freely admit, but what do I gain from putting my dev environment into a docker container that I don't get from just using a conventional VM - especially when I want access to physcal devices such as tills, sensors, remote servers etc. I can see use cases for small, independent server apps where you might need to spin up extra instances to improve load handling or to increase capacity. Or for starting up small web-based services quickly, being able to relocate them to other hardwre for failover etc, but I get all that already with existing VM technology... Don't get me wrong, I'm not saying it is rubbish, I just can't see how I could make effective use of it.
-
Interesting - espcially given the convoluted explanation I read hereabouts of how to get Netbeans to work in a docker container! I'm no expert on Docker I freely admit, but what do I gain from putting my dev environment into a docker container that I don't get from just using a conventional VM - especially when I want access to physcal devices such as tills, sensors, remote servers etc. I can see use cases for small, independent server apps where you might need to spin up extra instances to improve load handling or to increase capacity. Or for starting up small web-based services quickly, being able to relocate them to other hardwre for failover etc, but I get all that already with existing VM technology... Don't get me wrong, I'm not saying it is rubbish, I just can't see how I could make effective use of it.
Mike Winiberg wrote:
I'm not saying it is rubbish,
But you can. :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Checked out the 'Docker Challenge' page to see whats going on, and found only 4 articles posted in 6 weeks... Does it mean that Docker wasn't able to live up to the fuss of 'Anywhere' and 'Your Way'? Or we are to ignorant to try and understand something, that answers a need we never had?
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
