Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Contact
  • Reviews
  • Toggle search form
Home » Containers » The executor requires OSType=windows, but Docker Engine supports only OSType=linux

The executor requires OSType=windows, but Docker Engine supports only OSType=linux

Posted on 16/10/202121/12/2023 Christian By Christian 2 Comments on The executor requires OSType=windows, but Docker Engine supports only OSType=linux
Docker-OSTypelinux

This article describes the steps to resolve The executor requires OSType=windows, but Docker Engine supports only OSType=linux. GitLab Runner can use Docker to run jobs on user-provided images. This is possible with the use of a Docker executor. The Docker executor when used with GitLab CI, connects to Docker Engine and runs each build in a separate and isolated container using the predefined image that is set up in .gitlab-ci.yml and in accordance in config.toml.

That way you can have a simple and reproducible build environment that can also run on your workstation. Kindly refer to some of these related guides: How to install Git on macOS, how to clone a repository and install software from GitHub on Windows, Panic: Failed to register the GitLab-runner, you may be having network issues,

The added benefit is that you can test all the commands that we will explore later from your shell, rather than having to test them on a dedicated CI server.

The Docker executor when used with GitLab CI, connects to Docker Engine and runs each build in a separate and isolated container using the predefined image that is set up in it.

As you can see from the image below, I wasn’t using the “Docker-Windows” executor, but I was using the “Windows” executor only. When “windows” is used only, then the daemon should be Linux Container

concurrent = 1

check_interval = 0
[session_server]
session_timeout = 1800
[[runners]]
name = "windows10 runner with Docker-windows"
url = "https://gitlab.com/"
token = "pxxxxxxxxxxxxn"
executor = "docker"

This gave rise to the following error displayed below. Also, ensure you are using the right container environment.

Failed to remove network for build

Kindly refer to this troubleshooting guide for more information “Docker image OS” windows” cannot be used on this platform: No matching manifest for linux/amd64 in the manifest list entries from Microsoft Docker Registry“.

Solution – Ensure you are running the right executor

The executor was is “docker-windows“, this is because, the GitLab-runner is installed on Windows, and also we are using the Windows container. See the table below for more information.

GitLab runner

As you can see below, we have entered the right executor in the config.toml file. After this is done, ensure to restart both the GitLab-Runner and the Docker-Desktop. Kindly refer to this guide on “how to install, register and start GitLab Runner on Windows“.

concurrent = 1
check_interval = 0
[session_server]
session_timeout = 1800
[[runners]]
name = "windows10 runner with Docker-windows"
url = "https://gitlab.com/"
token = "pxxxxxxxxxxxxn"
executor = "docker-windows"

Kindly refer to these related guides: How to create and deploy a local Registry Server with Docker Image. And how to Pull your first Nginx Container Image from Docker Hub and deploy it to your local machine. Azure DevOps and GitHub integration for Docker and Kubernetes deployment. How to create a static pod in Kubernetes, and how to install, register and start GitLab Runner on Windows.

I hope you found this blog post on “The executor requires OSType=windows, but Docker Engine supports only OSType=linux” helpful. If you have any questions, please let me know in the comment session.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Containers Tags:docker, Docker Desktop, GitLab, GitLab-Runner, Windows 10

Post navigation

Previous Post: Docker image OS “windows” cannot be used on this platform: No matching manifest for linux/amd64 in the manifest list entries from Microsoft Docker Registry
Next Post: Failed to pull image with the policy “always” error from the daemon

Related Posts

  • GitLabrunner 1 1
    There has been a runner system failure: failed to start the process exec “pwsh” Containers
  • Windowsfilesystemxx
    Failed to remove network for the build, Job failed error: Invalid volume specification: “/cache” Containers
  • featurekube
    How to Install and Use Minikube on a Linux System Containers
  • Docker internal external
    Running Docker commands returns Docker is not recognized as an internal or external command Containers
  • How to configure Azure container register with secured connection with container apps
    Configure Azure Container Registry for a secure connection with Azure Container Apps AWS/Azure/OpenShift
  • Slide2
    How to Setup Jenkins Pipelines Environment for Docker Container Deployment Containers

More Related Articles

GitLabrunner 1 1 There has been a runner system failure: failed to start the process exec “pwsh” Containers
Windowsfilesystemxx Failed to remove network for the build, Job failed error: Invalid volume specification: “/cache” Containers
featurekube How to Install and Use Minikube on a Linux System Containers
Docker internal external Running Docker commands returns Docker is not recognized as an internal or external command Containers
How to configure Azure container register with secured connection with container apps Configure Azure Container Registry for a secure connection with Azure Container Apps AWS/Azure/OpenShift
Slide2 How to Setup Jenkins Pipelines Environment for Docker Container Deployment Containers

Comments (2) on “The executor requires OSType=windows, but Docker Engine supports only OSType=linux”

  1. Avatar photo Mesfun Habtab says:
    27/02/2023 at 9:10 AM

    Hello,

    I face other issues If I change to docker-windows as executor. Can we discuss this?

    Log in to Reply
    1. chris Christian says:
      06/03/2023 at 8:05 PM

      What would you like us to discuss?

      Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • uninstalloffice
    Remove All Microsoft Office Apps from Mac Network | Monitoring
  • coding
    Git GUI and Gitk won’t open “Missing Tcl / Tk Aqua libraries” Version Control System
  • hero activedirectory
    Create and find Organisation Unit paths in AD Scripts
  • Stellar Exchange
    Exchange Recovery: Repair EDB Files and Recover Mailboxes Reviews
  • EC2
    How to Add and Format a New Virtual Disk to an EC2 Instance AWS/Azure/OpenShift
  • Azure Storage 1
    Azure CLI: How To Upload Batch Files to Azure Storage Account AWS/Azure/OpenShift
  • Featured image batch file.
    Retrieve Recent Windows Update: How to create batch script files Scripts
  • Slide1
    Read-only Files: Saving Files in VIM Editor on Linux/Unix-like OS Linux

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,821 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.