Segfault in unshare when using an authenticated proxy under Windows 10

FredPraca commented 7 months ago

Issue Description

When using an authenticated proxy under Windows 10, during podman machine start, the following error message appears:

PS C:\WINDOWS\system32> podman machine start
Starting machine "podman-machine-default"
/root/bootstrap: line 4:   163 Segmentation fault      nohup unshare --kill-child --fork --pid --mount --mount-proc --propagation shared /lib/systemd/systemd > /dev/null 2>&1

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 for Docker API clients is not available due to the following startup failures.
        could not start api proxy since expected pipe is not available: podman-machine-default

Podman clients are still able to connect.
Machine "podman-machine-default" started successfully
PS C:\WINDOWS\system32> wsl

Steps to reproduce the issue

Specify the proxy, for example, in podman-desktop, using the form _http://url_encoded_username>:<url_encoded_password>@<proxy_ip:_
execute podman machine init
execute podman machine start

Describe the results you received

When launching, the following error message appears:

PS C:\WINDOWS\system32> podman machine start
Starting machine "podman-machine-default"
/root/bootstrap: line 4:   163 Segmentation fault      nohup unshare --kill-child --fork --pid --mount --mount-proc --propagation shared /lib/systemd/systemd > /dev/null 2>&1

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 for Docker API clients is not available due to the following startup failures.
        could not start api proxy since expected pipe is not available: podman-machine-default

Podman clients are still able to connect.

Podman is inaccessible from Windows Powershell or from Podman Desktop. Inside the WSL, Podman is working correctly

Describe the results you expected

Podman machine should not crash at launch and should be visible from Podman Desktop or Powershell

podman info output

PS C:\WINDOWS\system32> podman --version
podman.exe version 4.9.2

Under Windows 10 version 22H2 (build 19045.3930) on x86_64

Using Podman Desktop 1.7.1

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional information

Launching without providing a proxy runs without any Segmentation fault

github-actions[bot] commented 6 months ago

A friendly reminder that this issue had no activity for 30 days.

lwk694 commented 2 months ago

Issue Description

When using an authenticated proxy under Windows 10, during podman machine start, the following error message appears:
PS C:\WINDOWS\system32> podman machine start
Starting machine "podman-machine-default"
/root/bootstrap: line 4:   163 Segmentation fault      nohup unshare --kill-child --fork --pid --mount --mount-proc --propagation shared /lib/systemd/systemd > /dev/null 2>&1

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 for Docker API clients is not available due to the following startup failures.
        could not start api proxy since expected pipe is not available: podman-machine-default

Podman clients are still able to connect.
Machine "podman-machine-default" started successfully
PS C:\WINDOWS\system32> wsl
Steps to reproduce the issue

Steps to reproduce the issue

Specify the proxy, for example, in podman-desktop, using the form _http://url_encoded_username>:<url_encoded_password>@<proxy_ip:proxy:port_

execute podman machine init

execute podman machine start

Describe the results you received

When launching, the following error message appears:
PS C:\WINDOWS\system32> podman machine start
Starting machine "podman-machine-default"
/root/bootstrap: line 4:   163 Segmentation fault      nohup unshare --kill-child --fork --pid --mount --mount-proc --propagation shared /lib/systemd/systemd > /dev/null 2>&1

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 for Docker API clients is not available due to the following startup failures.
        could not start api proxy since expected pipe is not available: podman-machine-default

Podman clients are still able to connect.
Podman is inaccessible from Windows Powershell or from Podman Desktop. Inside the WSL, Podman is working correctly

Describe the results you expected

Podman machine should not crash at launch and should be visible from Podman Desktop or Powershell

podman info output
PS C:\WINDOWS\system32> podman --version
podman.exe version 4.9.2

Under Windows 10 version 22H2 (build 19045.3930) on x86_64

Using Podman Desktop 1.7.1
Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Launching without providing a proxy runs without any Segmentation fault

Hi I encountered same error as yours. How do you solve it?

FredPraca commented 2 months ago

By switching to Linux :) Moreover, it seems that some colleagues don't have this problem

containers / podman