GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing actuated.com — Actuated for GitLab CI - Secure, Fast microVM Runners GitLab.com & Self-hosted GitLab CI Blazing fast GitLab CIwithout the complexity.Secure, ephemeral Firecracker microVMs for every job. No Kubernetes to manage. No Docker In Docker security nightmares. Just fast, isolated builds on your own infrastructure. Faster BuildsBare-metal performance with builds typically 2-3x faster than hosted runners. No K8s to ManageNo Helm charts, no Kubernetes clusters. Just install our agent on bare-metal or VMs. No DIND NightmaresRun Docker natively in each microVM. No privileged containers, no socket binding. Instant BootVMs boot and start running jobs in under 1 second. Faster than Kubernetes pod scheduling. Two supported modesWhether you use GitLab.com or run GitLab on your own infrastructure, Actuated has you covered. GitLab.comConnect your own servers as runners for GitLab.com projects. Get bare-metal speed with the convenience of GitLab's hosted platform.
GitLab CI (Self-hosted)Run Actuated alongside your self-hosted GitLab instance. Full control over your CI infrastructure with enterprise-grade isolation.
How it worksWhen a pipeline is triggered, the Actuated control plane launches a dedicated Firecracker microVM for every job. The VM boots in under a second, runs the job, then is destroyed completely.
1 2 3 4   Security notice displayed by the GitLab Helm chart warning against Docker in Docker. Say goodbye to DINDDocker-in-Docker (DIND) requires privileged mode. The GitLab Helm chart disables it by default for good reason - it's a significant security risk. With Actuated, Docker runs natively inside each microVM. No privileged containers, no socket binding from the host, no flakey VFS driver. No need to switch to Kaniko, Buildah, or fight with user namespaces. You get Everything you need for GitLab CIFaster builds with bare-metal performance No Kubernetes cluster to manage No Docker In Docker (DIND) security nightmares Instant boot - VMs ready in under 1 second Ephemeral microVMs destroyed after every job Mixed Docker and Shell executors Flexible VM sizing per job via tags Private peering for on-premises networks Simple to configureAdd the Switch between Docker and Shell executors per-job by adding the .gitlab-ci.yml See it in actionWatch Actuated launch parallel GitLab CI jobs in dedicated Firecracker microVMs - each booting in under a second. Demo: Actuated for GitLab CI
Run anywhere with KVM supportActuated works with bare-metal servers and nested virtualisation across all major providers. AWSEC2 bare-metal or nested virtualisation AzureBare-metal or nested virtualisation GCPBare-metal or nested virtualisation OpenStackKVM-enabled instances VMwareNested virtualisation support On-premisesYour own data centre hardware Bare-metalDedicated servers from any provider Private peering for enterpriseServers behind a private network? Enable peering for an outbound connection that passes through firewalls, NAT, HTTP Proxies and VPNs without additional configuration.
 Learn moreJuly 2024 Secure your GitLab jobs with microVMs and ActuatedFeature overview including mixed executors, VM sizing, private peering, and how microVMs provide more flexibility and security for CI workloads. June 2023 Secure CI for GitLab with Firecracker microVMsThe original announcement for Actuated for GitLab CI, including a video demo and details on why Firecracker provides the isolation CI needs. Ready to speed up your GitLab CI?No sales pitch, just a quick chat with our engineers. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |