41–49 of 49 posts
Earlier quoted context omitted.
Wow, so does it mean even Docker workers thought having such a service like InstaDocker would be great at some time?
I thought it was a great demonstration of the technology, and there are a number of people/companies who came to the same conclusion.
Really great implementation. I was delighted to see that clicking on the 'Run Now' button immediately launched a container - no sign in, etc required. I've been working on a similar idea for running docker containers on a cron schedule. I use them for data processing, and web crawling, but don't have a good way to manage their schedules / logs. Right now I run everything off a single box with a cron schedule for each…
Really great implementation. I was delighted to see that clicking on the 'Run Now' button immediately launched a container - no sign in, etc required. I've been working on a similar idea for running docker containers on a cron schedule. I use them for data processing, and web crawling, but don't have a good way to manage their schedules / logs. Right now I run everything off a single box with a cron schedule for each…
Thank you very much! Scheduling could be an interesting feature. Why do you schedule your containers? Have you tried another approach?
Examples:
1. Crawl a website, and store the data to a database - update every few hours.
2. Check a website for changes.
3. Process log data, and save it to another location.
Docker may be overkill for some of these, but it provides a simple way to launch a new task in a container with all dependencies installed. The overhead seems to be relatively small for starting a new container, so it's worth the overhead vs. configuring a machine to run the container.
"This container will be alive for next 15 minutes. If you would like to keep it running more than 15 minutes please contact us on Twitter." - Changing 12 hours to 15 minutes, is the server overloaded?
We already receive a lot of interest but we just wanted to have more engagement on Twitter too :) We hit 300Mbps on our traffic and 30% on our CPU load. So, we still have more resources to serve. Also, our clusters are waiting to be spinned. Do you have any other recommendations to handle those requests and processes?
Earlier quoted context omitted.
Thank you very much! Scheduling could be an interesting feature. Why do you schedule your containers? Have you tried another approach?
I schedule them so I can run a recurring task every day. Examples: 1. Crawl a website, and store the data to a database - update every few hours. 2. Check a website for changes. 3. Process log data, and save it to another location. Docker may be overkill for some of these, but it provides a simple way to launch a new task in a container with all dependencies installed. The overhead seems to be relatively small for st…
Earlier quoted context omitted.
We already receive a lot of interest but we just wanted to have more engagement on Twitter too :) We hit 300Mbps on our traffic and 30% on our CPU load. So, we still have more resources to serve. Also, our clusters are waiting to be spinned. Do you have any other recommendations to handle those requests and processes?
15 minutes seems reasonable to me. I thought the original 12 hours was too long - I was done with the container I spun up a few minutes after I started it.
This sounds like a REALLY bad idea. Docker is not really meant to run untrusted images.
Here is the simpler one which is a backend for a barely started mobile front end.
https://github.com/runvnc/oicapp
I basically came to the conclusion that for scale simplicity and security I needed a new Digital Ocean VPS for each container so that's what I did. To make it faster you could sort of pool them ahead of time.