We use cookies and similar technologies to improve your experience, analyze site traffic, and personalize content. By clicking "Accept All", you consent to our use of cookies. You can manage your preferences or learn more in our Privacy Policy.
Privacy & Cookie Settings
We respect your privacy and give you control over your data. Choose which cookies you want to allow:
These cookies are necessary for the website to function and cannot be disabled. They are set in response to actions made by you such as setting your privacy preferences, logging in, or filling in forms.
These cookies help us understand how visitors interact with our website by collecting and reporting information anonymously. This helps us improve our services.
Providers: Google Analytics, Plausible Analytics (privacy-friendly)
These cookies are used to track visitors across websites to display relevant advertisements and measure campaign effectiveness.
Providers: LinkedIn, Twitter/X, Reddit
These cookies enable the website to remember choices you make (such as your language preference or region) to provide enhanced, more personalized features.
Your Privacy Rights
Right to Access: You can request a copy of your personal data
Right to Deletion: You can request deletion of your data
Right to Object: You can object to processing of your data
Right to Portability: You can request your data in a portable format
The runC vulnerability changed everything. A battle-hardened guide to securing container runtimes, locking down privileges, and why KVM isolation is your only real defense against kernel exploits.
Containers aren't magic security boxes. From the recent runC vulnerability to kernel isolation, we break down how to secure your stack using 2019's best practices, leveraging strict KVM boundaries and immutable infrastructure principles.
Default Docker configurations are a security nightmare waiting to explode. We break down how to lock down your container infrastructure, navigate Norwegian GDPR requirements, and why strict kernel isolation on CoolVDS is your last line of defense.
Default Docker settings are a security nightmare waiting to happen. In this 2018 guide, we dissect kernel isolation, drop capabilities, and secure the runtime to satisfy the Datatilsynet without sacrificing NVMe performance.
Default Docker settings are a security nightmare waiting to happen. Learn how to harden your container runtime, manage capabilities, and ensure GDPR compliance on high-performance Norwegian infrastructure.
Is Kubernetes overkill for your workload? We compare the state of orchestration in late 2018, analyzing overhead, complexity, and the specific infrastructure requirements needed to run them in Norway.
It is late 2018, and everyone is rushing to containerize. But if you are running as root in production, you are begging for a kernel breach. Here is the battle-tested guide to hardening your stack in Norway's threat landscape.
Containers are not Virtual Machines. Learn how to secure your Docker pipeline against privilege escalation and dirty images while navigating GDPR compliance in Norway. A technical guide for DevOps engineers.
Default Docker settings are a security nightmare waiting to happen. From dropping kernel capabilities to navigating GDPR compliance in Norway, here is how to harden your container infrastructure before you hit production.
It is 2018, and default Docker settings are not safe for production. From dropping capabilities to navigating the new GDPR landscape in Norway, here is how to lock down your container infrastructure.
It is July 2018. Everyone wants Kubernetes, but few need the headache. We benchmark the big three orchestrators against the reality of latency, GDPR, and disk I/O.
With the GDPR deadline just days away, choosing the right container orchestrator isn't just about 'cool factor'—it's about compliance and control. We benchmark Kubernetes 1.10 against Docker Swarm on Norwegian KVM infrastructure.
With the GDPR deadline looming on May 25th, choosing the right container orchestrator is about more than just features—it's about compliance, latency, and survival. We pit Kubernetes 1.10 against Docker Swarm to see which stack belongs on your Norwegian infrastructure.
With the May 2018 GDPR deadline looming and Meltdown/Spectre still haunting sysadmins, default Docker configurations are a liability. Here is the battle-hardened guide to securing containers on Norwegian infrastructure.
While the industry rushes toward Kubernetes, we benchmark complexity against raw performance. Discover why disk I/O latency is the hidden killer of container orchestration and how to architect a GDPR-ready cluster in Norway.
As the GDPR deadline looms in May 2018, Nordic DevOps teams are scrambling to containerize. We benchmark Kubernetes 1.9 against Docker Swarm to see which orchestrator offers the best balance of complexity versus control on Norwegian infrastructure.
With the GDPR deadline looming and CPU vulnerabilities exposing shared kernels, reliable container orchestration requires more than just 'docker run'. We analyze kernel isolation, capabilities dropping, and why KVM-backed VPS infrastructure is the only safe harbor for Norwegian data.
In the heat of the 2017 container wars, choosing between Kubernetes and Docker Swarm determines your infrastructure's fate. We analyze performance, complexity, and why underlying hardware like NVMe storage is critical for cluster stability.
It is May 2017. The container wars are raging. We benchmark Kubernetes 1.6 against Docker Swarm Mode to see which orchestrator offers the best balance of sanity, performance, and persistence on Norwegian infrastructure.
We compare Kubernetes 1.6 and Docker Swarm Mode for production workloads. Discover why underlying KVM infrastructure and NVMe storage are critical for container performance in the looming GDPR era.
Forget AWS Lambda cold starts and unpredictable billing. Learn how to architect a latency-crushing, private FaaS cluster using Docker Swarm and OpenFaaS on CoolVDS NVMe instances in Oslo. Total control, zero lock-in.
Default Docker configurations are dangerous. Learn how to drop capabilities, enforce non-root users, and isolate kernels to satisfy Datatilsynet and sleep at night.
Containers are not magic security boxes. From kernel exploits to network breaches, here is how to harden your Docker stack before the GDPR deadline hits.
Cloud providers promise nirvana with 'Serverless', but the latency and vendor lock-in can kill your architecture. Here is how to build a high-performance FaaS platform on Norwegian infrastructure using Docker and OpenFaaS.
We benchmark the complexity and performance of Kubernetes 1.5 against Docker Swarm Mode. Learn which orchestrator fits your Norwegian infrastructure stack before the GDPR deadline hits.
Is your deployment pipeline an excuse for a coffee break? We dissect the I/O bottlenecks killing your build times, implement ephemeral Docker agents, and optimize Jenkins 2.0 pipelines for the Nordic infrastructure landscape.
We analyze the Dirty COW aftermath, user namespaces in Docker 1.12, and why true KVM isolation on Norwegian soil is your only defense against shared-kernel vulnerabilities.
We benchmark Docker 1.12 Swarm Mode against Kubernetes 1.4 for high-availability Nordic infrastructure. Stop guessing and start architecting for stability.
The recent Dirty COW exploit was a wake-up call: containers are not sandboxes. In this deep dive, we explore how to harden Docker 1.12, manage kernel capabilities, and why running containers inside KVM slices is the only way to sleep at night.
The 'Dirty COW' exploit woke everyone up. Here is a battle-tested guide to locking down containers on Linux, why KVM is mandatory for true isolation, and how to navigate Norwegian data privacy in late 2016.