Is Docker appropriate for a long term server application? [closed]
Consider a single big server running multiple services on FreeBSD such as Plex, OpenVPN, Nextcloud, etc, with each service running in a jail.
Would Docker be appropriate as a Linux analogue to such a configuration?
I've never used Docker or other container solutions, but from what I gather from reading online, Docker containers are better suited for short term uses - being able to start a fresh server, kill it when you're done with it, and then pop up another brand new server when it's needed.
If the goal is to have an isolated service that runs continuously, changes frequently (new files uploaded to the containerized service, etc), and can be easily started and stopped as necessary in the same way as a FreeBSD jail, is Docker the right solution?
rhel docker
asked Mar 4 at 15:04
MellaMella
261112
closed as primarily opinion-based by Kusalananda♦, Rui F Ribeiro, Olorin, Thomas, jimmij Mar 5 at 8:09
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Consider a single big server running multiple services on FreeBSD such as Plex, OpenVPN, Nextcloud, etc, with each service running in a jail.
Would Docker be appropriate as a Linux analogue to such a configuration?
I've never used Docker or other container solutions, but from what I gather from reading online, Docker containers are better suited for short term uses - being able to start a fresh server, kill it when you're done with it, and then pop up another brand new server when it's needed.
If the goal is to have an isolated service that runs continuously, changes frequently (new files uploaded to the containerized service, etc), and can be easily started and stopped as necessary in the same way as a FreeBSD jail, is Docker the right solution?
rhel docker
asked Mar 4 at 15:04
MellaMella
261112
closed as primarily opinion-based by Kusalananda♦, Rui F Ribeiro, Olorin, Thomas, jimmij Mar 5 at 8:09
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
1
You seem to be familiar with FreeBSD jails. Why would that not be a suitable solution for you?
– Kusalananda♦
Mar 4 at 15:06
@Kusalananda I just prefer RHEL. I know FreeBSD, but RHEL is what I do at work, and I like to be able learn things from working on my server at home that can benefit me at work, and vice versa. It's just that jails happen to very nicely fit my home needs, but if I can get by with something else short of full on virtualizing everything, I'll do so.
– Mella
Mar 4 at 15:15
1
serverfault.com/questions/944354/…
– Michael D.
Mar 4 at 16:35
1
Many long term applications are deployed in docker containers, these days. A docker container has become the new "hotness" and is starting to replace VMware images.
– Stephen Harris
Mar 4 at 16:36
add a comment |
Consider a single big server running multiple services on FreeBSD such as Plex, OpenVPN, Nextcloud, etc, with each service running in a jail.
Would Docker be appropriate as a Linux analogue to such a configuration?
I've never used Docker or other container solutions, but from what I gather from reading online, Docker containers are better suited for short term uses - being able to start a fresh server, kill it when you're done with it, and then pop up another brand new server when it's needed.
If the goal is to have an isolated service that runs continuously, changes frequently (new files uploaded to the containerized service, etc), and can be easily started and stopped as necessary in the same way as a FreeBSD jail, is Docker the right solution?
rhel docker
asked Mar 4 at 15:04
MellaMella
261112
Consider a single big server running multiple services on FreeBSD such as Plex, OpenVPN, Nextcloud, etc, with each service running in a jail.
Would Docker be appropriate as a Linux analogue to such a configuration?
I've never used Docker or other container solutions, but from what I gather from reading online, Docker containers are better suited for short term uses - being able to start a fresh server, kill it when you're done with it, and then pop up another brand new server when it's needed.
If the goal is to have an isolated service that runs continuously, changes frequently (new files uploaded to the containerized service, etc), and can be easily started and stopped as necessary in the same way as a FreeBSD jail, is Docker the right solution?
rhel docker
rhel docker
asked Mar 4 at 15:04
MellaMella
261112
asked Mar 4 at 15:04
MellaMella
261112
asked Mar 4 at 15:04
MellaMella
261112
asked Mar 4 at 15:04
MellaMella
261112
asked Mar 4 at 15:04
MellaMella
261112
261112
closed as primarily opinion-based by Kusalananda♦, Rui F Ribeiro, Olorin, Thomas, jimmij Mar 5 at 8:09
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as primarily opinion-based by Kusalananda♦, Rui F Ribeiro, Olorin, Thomas, jimmij Mar 5 at 8:09
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
1
You seem to be familiar with FreeBSD jails. Why would that not be a suitable solution for you?
– Kusalananda♦
Mar 4 at 15:06
@Kusalananda I just prefer RHEL. I know FreeBSD, but RHEL is what I do at work, and I like to be able learn things from working on my server at home that can benefit me at work, and vice versa. It's just that jails happen to very nicely fit my home needs, but if I can get by with something else short of full on virtualizing everything, I'll do so.
– Mella
Mar 4 at 15:15
1
serverfault.com/questions/944354/…
– Michael D.
Mar 4 at 16:35
1
Many long term applications are deployed in docker containers, these days. A docker container has become the new "hotness" and is starting to replace VMware images.
– Stephen Harris
Mar 4 at 16:36
add a comment |
1
You seem to be familiar with FreeBSD jails. Why would that not be a suitable solution for you?
– Kusalananda♦
Mar 4 at 15:06
@Kusalananda I just prefer RHEL. I know FreeBSD, but RHEL is what I do at work, and I like to be able learn things from working on my server at home that can benefit me at work, and vice versa. It's just that jails happen to very nicely fit my home needs, but if I can get by with something else short of full on virtualizing everything, I'll do so.
– Mella
Mar 4 at 15:15
1
serverfault.com/questions/944354/…
– Michael D.
Mar 4 at 16:35
1
Many long term applications are deployed in docker containers, these days. A docker container has become the new "hotness" and is starting to replace VMware images.
– Stephen Harris
Mar 4 at 16:36
1
1
You seem to be familiar with FreeBSD jails. Why would that not be a suitable solution for you?
– Kusalananda♦
Mar 4 at 15:06
You seem to be familiar with FreeBSD jails. Why would that not be a suitable solution for you?
– Kusalananda♦
Mar 4 at 15:06
@Kusalananda I just prefer RHEL. I know FreeBSD, but RHEL is what I do at work, and I like to be able learn things from working on my server at home that can benefit me at work, and vice versa. It's just that jails happen to very nicely fit my home needs, but if I can get by with something else short of full on virtualizing everything, I'll do so.
– Mella
Mar 4 at 15:15
@Kusalananda I just prefer RHEL. I know FreeBSD, but RHEL is what I do at work, and I like to be able learn things from working on my server at home that can benefit me at work, and vice versa. It's just that jails happen to very nicely fit my home needs, but if I can get by with something else short of full on virtualizing everything, I'll do so.
– Mella
Mar 4 at 15:15
1
1
serverfault.com/questions/944354/…
– Michael D.
Mar 4 at 16:35
serverfault.com/questions/944354/…
– Michael D.
Mar 4 at 16:35
1
1
Many long term applications are deployed in docker containers, these days. A docker container has become the new "hotness" and is starting to replace VMware images.
– Stephen Harris
Mar 4 at 16:36
Many long term applications are deployed in docker containers, these days. A docker container has become the new "hotness" and is starting to replace VMware images.
– Stephen Harris
Mar 4 at 16:36
add a comment |
1 Answer
1
active
oldest
votes
Conceptually, Docker containers use Linux namespaces, which are similar to FreeBSD jails.
In addition, Docker containers make it easy to to incrementally add "layers" with files, so you can quickly get a standardized environment to execute whatever services you need. While these layers are considered static, and you'd deploy a new container if there are changes to this environment, you can also mount different stuff into the Docker container, and change files inside that as frequently as you want.
There's no big problem with running a Docker container for a long time. However, Docker containers really shine if you need to scale your application: You can deploy as many copies of a container on different host machines machines as you want, all driven by demand, and Docker abstracts over this so the containers don't really notice on how many physical hosts they run.
So if you have multiple services, you'd typically run each inside its own container.
I'm not sure if this answers the question. Maybe the best way to learn about it is to try to make or deploy a few Docker containers of your own, and see if it suits your needs.
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Conceptually, Docker containers use Linux namespaces, which are similar to FreeBSD jails.
In addition, Docker containers make it easy to to incrementally add "layers" with files, so you can quickly get a standardized environment to execute whatever services you need. While these layers are considered static, and you'd deploy a new container if there are changes to this environment, you can also mount different stuff into the Docker container, and change files inside that as frequently as you want.
There's no big problem with running a Docker container for a long time. However, Docker containers really shine if you need to scale your application: You can deploy as many copies of a container on different host machines machines as you want, all driven by demand, and Docker abstracts over this so the containers don't really notice on how many physical hosts they run.
So if you have multiple services, you'd typically run each inside its own container.
I'm not sure if this answers the question. Maybe the best way to learn about it is to try to make or deploy a few Docker containers of your own, and see if it suits your needs.
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
add a comment |
Conceptually, Docker containers use Linux namespaces, which are similar to FreeBSD jails.
In addition, Docker containers make it easy to to incrementally add "layers" with files, so you can quickly get a standardized environment to execute whatever services you need. While these layers are considered static, and you'd deploy a new container if there are changes to this environment, you can also mount different stuff into the Docker container, and change files inside that as frequently as you want.
There's no big problem with running a Docker container for a long time. However, Docker containers really shine if you need to scale your application: You can deploy as many copies of a container on different host machines machines as you want, all driven by demand, and Docker abstracts over this so the containers don't really notice on how many physical hosts they run.
So if you have multiple services, you'd typically run each inside its own container.
I'm not sure if this answers the question. Maybe the best way to learn about it is to try to make or deploy a few Docker containers of your own, and see if it suits your needs.
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
add a comment |
Conceptually, Docker containers use Linux namespaces, which are similar to FreeBSD jails.
In addition, Docker containers make it easy to to incrementally add "layers" with files, so you can quickly get a standardized environment to execute whatever services you need. While these layers are considered static, and you'd deploy a new container if there are changes to this environment, you can also mount different stuff into the Docker container, and change files inside that as frequently as you want.
There's no big problem with running a Docker container for a long time. However, Docker containers really shine if you need to scale your application: You can deploy as many copies of a container on different host machines machines as you want, all driven by demand, and Docker abstracts over this so the containers don't really notice on how many physical hosts they run.
So if you have multiple services, you'd typically run each inside its own container.
I'm not sure if this answers the question. Maybe the best way to learn about it is to try to make or deploy a few Docker containers of your own, and see if it suits your needs.
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
Conceptually, Docker containers use Linux namespaces, which are similar to FreeBSD jails.
In addition, Docker containers make it easy to to incrementally add "layers" with files, so you can quickly get a standardized environment to execute whatever services you need. While these layers are considered static, and you'd deploy a new container if there are changes to this environment, you can also mount different stuff into the Docker container, and change files inside that as frequently as you want.
There's no big problem with running a Docker container for a long time. However, Docker containers really shine if you need to scale your application: You can deploy as many copies of a container on different host machines machines as you want, all driven by demand, and Docker abstracts over this so the containers don't really notice on how many physical hosts they run.
So if you have multiple services, you'd typically run each inside its own container.
I'm not sure if this answers the question. Maybe the best way to learn about it is to try to make or deploy a few Docker containers of your own, and see if it suits your needs.
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
answered Mar 5 at 7:50
dirktdirkt
17.4k31338
17.4k31338
add a comment |
add a comment |
1
You seem to be familiar with FreeBSD jails. Why would that not be a suitable solution for you?
– Kusalananda♦
Mar 4 at 15:06
@Kusalananda I just prefer RHEL. I know FreeBSD, but RHEL is what I do at work, and I like to be able learn things from working on my server at home that can benefit me at work, and vice versa. It's just that jails happen to very nicely fit my home needs, but if I can get by with something else short of full on virtualizing everything, I'll do so.
– Mella
Mar 4 at 15:15
1
serverfault.com/questions/944354/…
– Michael D.
Mar 4 at 16:35
1
Many long term applications are deployed in docker containers, these days. A docker container has become the new "hotness" and is starting to replace VMware images.
– Stephen Harris
Mar 4 at 16:36