Server4You Review
-
Not offering console access is pretty common. Amazon and Azure don't offer console either. DO, RS and Vultr do.
-
The only time I figure that would be a problem is if the system needs to run fsck or something and it hangs the boot process. (I've had this happen twice at C@C this week... thus my reason for switching, finally).
-
I guess that sometimes even "I already paid for it" just is not good enough!
-
@Reid-Cooper Ha ha hah a. Yeah.... but I'm in a much better place now. I could probably do a bunch of docker containers for various apps and all once I get that deep in.
-
That would be very cool. Can you use Docker with a service like this? How does it handle the extra IPs for the Docker containers?
-
@Reid-Cooper I am not sure yet. I figure the only thing that I need to figure out is the multiple IP addresses.
I wonder if OpenVZ may be better to test in an environment like this.
-
@dafyre said:
@Reid-Cooper I am not sure yet. I figure the only thing that I need to figure out is the multiple IP addresses.
I wonder if OpenVZ may be better to test in an environment like this.
Docker and OpenVZ are pretty similar. I think if you can solve the multiple-IP address issue either will work just fine.
-
@Reid-Cooper said:
That would be very cool. Can you use Docker with a service like this? How does it handle the extra IPs for the Docker containers?
You can do a proxy with nginx and have it link to the containers.
-
@johnhooks said:
@Reid-Cooper said:
That would be very cool. Can you use Docker with a service like this? How does it handle the extra IPs for the Docker containers?
You can do a proxy with nginx and have it link to the containers.
That only works if you are doing web pages.
-
@johnhooks Good idea!
I need to spend some time with NginX and see how it fares with my OwnCloud instance.
-
@scottalanmiller you can link the containers together via a port and then nginx to the front facing container. Everything else you just link the containers with a throwaway container to control it and the delete that extra one.
-
@johnhooks said:
@scottalanmiller you can link the containers together via a port and then nginx to the front facing container. Everything else you just link the containers with a throwaway container to control it and the delete that extra one.
Not sure that I understand what you are saying. The individual containers act like individual VMs. But nGinx just does web not "any" traffic.
-
@scottalanmiller said:
@johnhooks said:
@scottalanmiller you can link the containers together via a port and then nginx to the front facing container. Everything else you just link the containers with a throwaway container to control it and the delete that extra one.
Not sure that I understand what you are saying. The individual containers act like individual VMs. But nGinx just does web not "any" traffic.
Right but you don't really access them via IP unless they're web facing containers. Like MySQL for example. You would create a MySQL container and then create another MySQL container to attach to it with the MySQL prompt. Then create your database, and then delete the second mysql container. Then you link your web app to the original MySQL container and that's how it accesses the database. All of that is done from the host. The only thing you would really be accessing via IP would be something over http. The containers don't even really need a public facing port number, you can link them behind nginx and then use an upstream block to access each http site or app.
-
Are you just pointing out that you can create a private, inaccessible network? Of course, you can build your own private addressing.
-
@scottalanmiller said:
Are you just pointing out that you can create a private, inaccessible network? Of course, you can build your own private addressing.
What would you be accessing container wise via IP that's not over http?
-
@johnhooks said:
What would you be accessing container wise via IP that's not over http?
Tons of things. Storage servers, VPN servers, Remote Desktop, SSH, databases, etc. Anything that isn't a web page. HTTP is popular but hardly the only application protocol out there.
-
Why does it being a container make HTTP assumed?
-
@scottalanmiller said:
Why does it being a container make HTTP assumed?
It's not but all of those things are done from the host. Not the public facing IP address.
-
You would SSH into the host and do a docker exec -it <container name or Id> /bin/bash
-
@johnhooks said:
@scottalanmiller said:
Why does it being a container make HTTP assumed?
It's not but all of those things are done from the host. Not the public facing IP address.
Why would those things be from the host? Why run Docker if you bypass it and run services elsewhere?
