You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to run Podman machine to use with Azure devops build agent - Failed to configure network (networkingMode Nat), falling back to VirtioProxy
#25283
Closed
nddipiazza opened this issue
Feb 10, 2025
· 2 comments
Starting machine "podman-machine-default"
Starting user-mode networking...
wsl: Failed to configure network (networkingMode Nat), falling back to networkingMode VirtioProxy.
your 131072x1 screen size is bogus. expect trouble
your 131072x1 screen size is bogus. expect trouble
This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:
podman machine set --rootful
API forwarding listening on: npipe:////./pipe/docker_engine
Docker API clients default to this address. You do not need to set DOCKER_HOST.
Machine "podman-machine-default" started successfully
Trying to pull quay.io/podman/hello:latest...
Error: initializing source docker://quay.io/podman/hello:latest: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp: lookup quay.io: Temporary failure in name resolution
##[error]PowerShell exited with code '1'.
I am not able to query quay.io from my podman container.
Note that the MyServiceAccountHere user that is running the process is not an actually logged in user. They are a service account that runs the Azure Devops agent service process.
How do I allow this Pipeline-like access to work?
The text was updated successfully, but these errors were encountered:
Discussed in #25279
Originally posted by nddipiazza February 10, 2025
I have a local On-Prem Azure Devops instance with Windows build agents
I'd like to utilize Podman from these Windows build agents so that I can utilize Podman inside my Azure Devops pipelines.
I am running a podman machine like so:
podman machine info
Here are the Podman commands I'm doing:
Result:
I am not able to query quay.io from my podman container.
Note that the
MyServiceAccountHere
user that is running the process is not an actually logged in user. They are a service account that runs the Azure Devops agent service process.How do I allow this Pipeline-like access to work?
The text was updated successfully, but these errors were encountered: