• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.


Search the Community

Showing results for tags 'containers'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • vpsBoard
    • Announcements & Contests
    • Industry News
  • Virtual Private Servers
    • General Talk
    • Operating a VPS Business
    • Tutorials and Guides
    • Questions and Answers
  • The Lounge
    • The Pub (Off topic discussion)
    • Coding, Scripting & Programming
    • SBC, ARM, Home Automation
  • Marketplace & Reviews
    • Reviews
    • VPS Offers
    • Other Offers
    • Service Requests

Found 5 results

  1. I have multiple web sites (and a few other processes) I want to run in an environment that is flexible and as low maintenance as possible. This includes my sites and customer sites, production and development. Most share a common platform (Python, Django, Postgres, Linux (mostly Debian)). I need to be able to give At the moment they are all running in separate VPSs, and some on shared hosting. The problem with multiple unmanaged VPSs is that it is a lot of stuff to manage. I have been experimenting with running the sites on a single VPS with multiple users. It is a "cloud" one so can be scaled up as needed, and there is only one OS and shared libraries to upgrade. The problem is relying on permissions to separate sites from each other, and to give users access to sites is quite fiddly, particularly as I am paranoid enough to run app servers as a different user from the code they exectute. I have not ruled it out as a solution, but it is not as straightforward as expected I thought of running my own VPSs on a dedi, which is cost effective, but adds one more component to manage. It gives me a lot of isolation. I think some sort of container or jail solution will give me the best of both worlds, but I am not familiar enough with it to pick suggestions? I am willing to consider using any *nix OS, although Debian Linux is what I am most familiar with. Resource isolation is not an issue: it will not be running anything I expect to cause problems. Easy admin and security are. Any suggestions?
  2. full study: https://insights.ubuntu.com/2015/05/18/lxd-crushes-kvm-in-density-and-speed/ LXD info: http://www.ubuntu.com/cloud/tools/lxd
  3. Hi, I am happy to announce the release of the Flockport mailserver which makes it easy for end users to deploy a mail server in any VPS (except OpenVZ) See the video walk through. Just like the mail server Flockport has containers of popular web apps that basically let users launch and use these apps without the need to install and configure web stacks and applications. Flockport containers are based on the open source LXC project. LXC is identical to OpenVZ, only its supported in the vanilla Linux kernel. A lot of our new users are not familiar with containers and have trouble understanding them conceptually and the flexibility and portability gained by decoupling your applications from the host OS. We have added a number of videos and tons of documentation to illustrate how easy it to use portable containers as a way to deploy applications.
  4. Hi All, I am thrilled to make this post here. I been have soaking up all the guides, especially by wlanboy for some time and have been used for some of the containers, and I hope Flockport is useful to the vpsboard community. Flockport provides ready to deploy containers of popular web apps, based on LXC. At launch there are over 40 containers including Wordpress, Drupal, Joomla, Prestashop, Moodle, Discourse, Redmine, Nodebb, Gitlab, a really nice mailserver and more, and we expect this to be augmented by the community. The advantage of Flockport containers is users don't have to configure and install apps. Just install LXC and you can deploy fully configured Flockport containers in seconds. And it works in cloud KVMs. Linux containers give users cloud like flexibility of app instances. For example for Vpsboard users who like to try new providers, with containers you are not wedded to any provider and can easily move your apps across Linux systems, and clone, deploy and backup in seconds. LXC is an open source project supported by Ubuntu. It quite simple to use, however thanks to its longish history (baking since 2009) a lot of information online is often outdated. It works out of the box in Ubuntu, with documentation and updated LXC packages often lacking in other distros. We like Debian so we have a repo for Debian wheezy with updated LXC packages that work out of the box, and tons of documentation to help users get started quickly. A little container context. LXC is of course not the only container technology. There is the popular OpenVZ and Linux Vserver but their growth has been impeded by the need of custom kernels. LXC is supported in the vanilla Linux kernel paving the way for widespread adoption. Docker untill 2 months ago was based on LXC. We have articles that clarify the differences between LXC and Docker and extra guides on container/VM networking scenarios which is an area that can trip users. Would absolutely love to hear the feedback of the informed community here!
  5. I doubt anyone here is crazy enough to be screwing around with UBC knobs and parameters ... but if you have an intimate relationship with "Burst RAM", OpenVZ is about to break up with you. https://lists.openvz.org/pipermail/announce/2014-July/000521.html Though it's pretty painless to make backups, upgrade the node & convert the containers, it can get pretty ... monotonous, if you're doing a lot of conversions at once. I'll sure lend a hand if I can...! :-) RIP - obtrusive, resource-sucking, memory-hogging, no vswap-having, privvmpages limit-exceeding, superfluous failcnt-generating, JVM incapable kernel.