Missuse Docker Container as VM
up vote
0
down vote
favorite
I've read that you shouldn't ssh into a docker container. But why? I'd like to use a docker container as a replacement for a normal VM. What are the disadvantages? I know that this will create a lot of layers. But I could flatten my container on a regular base.
Can I use the container as a regular vm and what is the "worst case" that can happen?
docker containers docker-container
asked Nov 21 at 19:31
Franken
378
add a comment |
up vote
0
down vote
favorite
I've read that you shouldn't ssh into a docker container. But why? I'd like to use a docker container as a replacement for a normal VM. What are the disadvantages? I know that this will create a lot of layers. But I could flatten my container on a regular base.
Can I use the container as a regular vm and what is the "worst case" that can happen?
docker containers docker-container
asked Nov 21 at 19:31
Franken
378
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've read that you shouldn't ssh into a docker container. But why? I'd like to use a docker container as a replacement for a normal VM. What are the disadvantages? I know that this will create a lot of layers. But I could flatten my container on a regular base.
Can I use the container as a regular vm and what is the "worst case" that can happen?
docker containers docker-container
asked Nov 21 at 19:31
Franken
378
I've read that you shouldn't ssh into a docker container. But why? I'd like to use a docker container as a replacement for a normal VM. What are the disadvantages? I know that this will create a lot of layers. But I could flatten my container on a regular base.
Can I use the container as a regular vm and what is the "worst case" that can happen?
docker containers docker-container
docker containers docker-container
asked Nov 21 at 19:31
Franken
378
asked Nov 21 at 19:31
Franken
378
asked Nov 21 at 19:31
Franken
378
asked Nov 21 at 19:31
Franken
378
asked Nov 21 at 19:31
Franken
378
378
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
No you can't use it as a replacement for a VM since you can only have one entrypoint on a docker container. You can not expose multiple services on multiple ports like you would on a regular virtual machine.
answered Nov 21 at 21:54
Tyler
176
1
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
add a comment |
up vote
0
down vote
Docker containers are optimized around running single processes. Virtual machines are optimized around running entire operating systems.
At a technical level you generally can run something that looks like a full VM inside a Docker container, but it's a lot of hand setup. For instance, a typical systemd setup wants to manage several host devices and kernel-level configuration options, and your choices to run systemd are either (a) let it manage the host and possibly conflict with the host's systemd, or (b) manually figure out which unit files you can't run and disable them. All of the prebuilt Docker images run only single services (just MySQL, just Nginx, just a Python runtime, ...) and so you're also giving up this ecosystem.
A VM certainly gives up some amount of efficiency by virtualizing hardware devices and running multiple OS kernels, but if you really want to run a VM, it's not a huge performance loss; just run a VM if that's the model you want to use.
answered Nov 22 at 19:13
David Maze
8,5182821
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
No you can't use it as a replacement for a VM since you can only have one entrypoint on a docker container. You can not expose multiple services on multiple ports like you would on a regular virtual machine.
answered Nov 21 at 21:54
Tyler
176
1
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
add a comment |
up vote
0
down vote
No you can't use it as a replacement for a VM since you can only have one entrypoint on a docker container. You can not expose multiple services on multiple ports like you would on a regular virtual machine.
answered Nov 21 at 21:54
Tyler
176
1
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
add a comment |
up vote
0
down vote
up vote
0
down vote
No you can't use it as a replacement for a VM since you can only have one entrypoint on a docker container. You can not expose multiple services on multiple ports like you would on a regular virtual machine.
answered Nov 21 at 21:54
Tyler
176
No you can't use it as a replacement for a VM since you can only have one entrypoint on a docker container. You can not expose multiple services on multiple ports like you would on a regular virtual machine.
answered Nov 21 at 21:54
Tyler
176
answered Nov 21 at 21:54
Tyler
176
answered Nov 21 at 21:54
Tyler
176
answered Nov 21 at 21:54
Tyler
176
176
1
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
add a comment |
1
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
1
1
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
I realy can't start Services in the background? What about using supervisord?
– Franken
Nov 21 at 22:39
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
What about daemons? If I start a Webserver there can't be a ntp daemon at the same time on the machine?
– Franken
Nov 21 at 22:45
add a comment |
up vote
0
down vote
Docker containers are optimized around running single processes. Virtual machines are optimized around running entire operating systems.
At a technical level you generally can run something that looks like a full VM inside a Docker container, but it's a lot of hand setup. For instance, a typical systemd setup wants to manage several host devices and kernel-level configuration options, and your choices to run systemd are either (a) let it manage the host and possibly conflict with the host's systemd, or (b) manually figure out which unit files you can't run and disable them. All of the prebuilt Docker images run only single services (just MySQL, just Nginx, just a Python runtime, ...) and so you're also giving up this ecosystem.
A VM certainly gives up some amount of efficiency by virtualizing hardware devices and running multiple OS kernels, but if you really want to run a VM, it's not a huge performance loss; just run a VM if that's the model you want to use.
answered Nov 22 at 19:13
David Maze
8,5182821
add a comment |
up vote
0
down vote
Docker containers are optimized around running single processes. Virtual machines are optimized around running entire operating systems.
At a technical level you generally can run something that looks like a full VM inside a Docker container, but it's a lot of hand setup. For instance, a typical systemd setup wants to manage several host devices and kernel-level configuration options, and your choices to run systemd are either (a) let it manage the host and possibly conflict with the host's systemd, or (b) manually figure out which unit files you can't run and disable them. All of the prebuilt Docker images run only single services (just MySQL, just Nginx, just a Python runtime, ...) and so you're also giving up this ecosystem.
A VM certainly gives up some amount of efficiency by virtualizing hardware devices and running multiple OS kernels, but if you really want to run a VM, it's not a huge performance loss; just run a VM if that's the model you want to use.
answered Nov 22 at 19:13
David Maze
8,5182821
add a comment |
up vote
0
down vote
up vote
0
down vote
Docker containers are optimized around running single processes. Virtual machines are optimized around running entire operating systems.
At a technical level you generally can run something that looks like a full VM inside a Docker container, but it's a lot of hand setup. For instance, a typical systemd setup wants to manage several host devices and kernel-level configuration options, and your choices to run systemd are either (a) let it manage the host and possibly conflict with the host's systemd, or (b) manually figure out which unit files you can't run and disable them. All of the prebuilt Docker images run only single services (just MySQL, just Nginx, just a Python runtime, ...) and so you're also giving up this ecosystem.
A VM certainly gives up some amount of efficiency by virtualizing hardware devices and running multiple OS kernels, but if you really want to run a VM, it's not a huge performance loss; just run a VM if that's the model you want to use.
answered Nov 22 at 19:13
David Maze
8,5182821
Docker containers are optimized around running single processes. Virtual machines are optimized around running entire operating systems.
At a technical level you generally can run something that looks like a full VM inside a Docker container, but it's a lot of hand setup. For instance, a typical systemd setup wants to manage several host devices and kernel-level configuration options, and your choices to run systemd are either (a) let it manage the host and possibly conflict with the host's systemd, or (b) manually figure out which unit files you can't run and disable them. All of the prebuilt Docker images run only single services (just MySQL, just Nginx, just a Python runtime, ...) and so you're also giving up this ecosystem.
A VM certainly gives up some amount of efficiency by virtualizing hardware devices and running multiple OS kernels, but if you really want to run a VM, it's not a huge performance loss; just run a VM if that's the model you want to use.
answered Nov 22 at 19:13
David Maze
8,5182821
answered Nov 22 at 19:13
David Maze
8,5182821
answered Nov 22 at 19:13
David Maze
8,5182821
answered Nov 22 at 19:13
David Maze
8,5182821
8,5182821
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419311%2fmissuse-docker-container-as-vm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
