[Feature Request] podman Windows WSL support #3288
Assignees
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/feature
|
@baude is this podman attempting to write events to the journal? |
|
We'll definitely need WSL 2. Ideally it works out of the box at that point,
though I suspect config file tweaking is going to be needed.
…On Mon, Jun 10, 2019, 06:02 Daniel J Walsh ***@***.***> wrote:
@baude <https://github.com/baude> is this podman attempting to write
events to the journal?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3288>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3AOCESVDRYGCHAVVYFZ4LPZYRBPANCNFSM4HWQIQ5Q>
.
|
|
yes, it is simply saying it cannot find journald. I don't believe the error is fatal. This can be remedied in a couple of different ways but the easiest would be to alter the event logger in libpod.conf. |
|
In fact, i wonder if we should include that in the error message? |
|
@baude I think that's a good suggestion. When I encountered, I couldn't figure out if it's fatal or not just from the error messages. |
|
BTW, here you can just change to file and it should help. https://github.com/containers/libpod/blob/master/libpod.conf#L104 |
|
is this still an issue? |
|
@baude yes |
|
I think that's probably WSL v1 (syscall emulation) not being able to do everything we need. |
|
Does --net=host work? |
|
Still the same |
|
Actually, I just noticed that the flags are supposed to be before "ubuntu". Now I'm getting a different error |
|
Need to default libpod.conf to use cgroupfs rather then systemd. Should fix this. |
|
I guess it's getting closer, one step at a time! =D |
|
With the release of WSL 2 (though only through the Insiders program thus far), I think we should be ready; I'd be interested to see someone try Podman on the new WSL and report back. |
|
So net=host is still required for the new WSL? Interesting.
…On Fri, Jun 14, 2019, 06:05 navigaid ***@***.***> wrote:
Adding --cgroup-manager=cgroupfs --net=host works for me.
***@***.*** YHX]# podman run --cgroup-manager=cgroupfs --net=host --rm -it ubuntu cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
For anyone interested, I'm using archlinux on WSL2 through
https://github.com/yuk7/ArchWSL
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3288>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3AOCD4SK4WI6F5IXZNJILP2NUNDANCNFSM4HWQIQ5Q>
.
|
|
Couple of notable items here, i tried wsl2 with ubuntu:
|
|
Does WSL Support User Namespace? --uidmap 0:100000:5000 |
|
Might want to see if we can pull the flags they compiled their kernel with - they might not be shipping userns-enabled kernels? |
|
results for uidmap |
|
It looks like the kernel supplied for WSL does not support user namespaces. |
|
Just tried on WSL2 Ubuntu |
|
Actually, "sudo" in front of the command worked |
|
I thought someone had confirmed that the Kernel used did not have User Namespace enabled, meaning rootless podman will not work. Someone should point out to Microsoft or Ubuntu or whoever that this should be enabled in the kernel. |
|
the kernel always comes from microsoft. and indeed, it does not support user namespace. so both rootless and rooted without --net=host fail. |
|
I guess we should file an issue to https://github.com/microsoft/WSL2-Linux-Kernel then? |
|
@kkimdev Could you take care of that? |
|
This may help microsoft/WSL#4165 |
|
@Biswa96 Thanks for the information! I just tried I'm not really familiar with the kernel/namespace stuff so I will back off from further investigation though. |
|
Does |
No I got the following on WSL 2. Also, |
|
Hello! The issue with podman is still ongoing, it throws an error about insufficient ids in namespace. Apparently there is no userids allocated for other than root. So for root it works. Possibly this mockbuild user has something to do with it? For root, I get an error when running a container about a journal socket |
|
Could you set the --event-logger=file. does that fix the root running problem? |
|
According to the above problem description and treatment methods, I still haven't solved the problem that podman started alpine container. Is there any new progress in this problem? ?
|
|
@baude @ashley-cui PTAL |
I am getting the exact same error on WSL. It doesn't matter what image you are trying to work with. Here's my example. Tried this as root on WSL Ubuntu 20.04 |
|
can you use wsl2? |
|
Currently with minor modifications, like this should work. However, there is no easy way to use |
This was referenced Feb 14, 2021
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
/kind feature
Description
Windows WSL support. Note that WSL 2 is expected to be released in June 2019
So probably worthwhile to wait first.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Successfully running Ubuntu container.
Output of
podman version:Output of
podman info --debug:The text was updated successfully, but these errors were encountered: