UI image does not work with Podman #594

rmarting · 2021-09-28T13:47:42Z

Describe the bug

The instructions (README.md file) describe how to start the UI using docker but it does not include how to do it with podman. When I started the container, the UI is available but any operation works (e.g: create an application, upload an artifact).

To Reproduce
Steps to reproduce the behavior:

Start the UI image with podman

~/Workspaces/ws-konveyor 
❯ mkdir -p workspace && cd workspace
Workspaces/ws-konveyor/workspace 
❯ podman run -p 8080:8080 -v $PWD:/workspace -it quay.io/konveyor/move2kube-aio:latest

See error:

FATA[0000] failed to setup the handlers. Error: "failed to make the workspaces metadata directory at path /workspace/data/metadata/workspaces . Error: \"mkdir /workspace/data: permission denied\"" 
[info   ] starting move2kube-ui in production mode.... 
[HPM] Proxy created: /  -> http://localhost:9000
[info   ] authentication is disabled 
[info   ] listening on port 8080

Expected behavior

Not FATAL messages and UI working successfully.

Desktop (please complete the following information):

OS: Fedora Workstation 34
Version: move2kube-aio:latest container image

The text was updated successfully, but these errors were encountered:

ashokponkumar · 2021-09-28T13:53:38Z

Thanks @rmarting for the issue. @HarikrishnanBalagopal Please take a look.

HarikrishnanBalagopal · 2021-09-28T13:55:32Z

@rmarting Hi, are you using the release version?
We have been working on v3 for a while now. Can you try the new commands in the README.md of the UI repo?
https://github.com/konveyor/move2kube-ui

1. Build the UI image: make cbuild
2. This uses docker and runs everything inside a single container using the UI image: make crun
3. Access the UI at http://localhost:8080

In this case you don't need to build, you can simply make crun after checking out the UI repo

ashokponkumar · 2021-09-28T14:04:43Z

@rmarting Can you please try podman run --rm -it -p 8080:8080 -v ${PWD}/data:/move2kube-api/data quay.io/konveyor/move2kube-ui:latest

HarikrishnanBalagopal · 2021-09-28T14:11:53Z

I have opened a PR to update the instructions in the README #595

rmarting · 2021-09-28T14:55:59Z

@HarikrishnanBalagopal I just opened other issue in move2kube-ui because the 'make' command does not working without `docker'. konveyor/move2kube-ui#97

rmarting · 2021-09-28T15:01:23Z

@ashokponkumar Your command does not work in my laptop. It seems that mount volumes with podman is something not simple as in docker.

❯ podman run --rm -it -p 8080:8080 -v ${PWD}/data:/move2kube-api/data quay.io/konveyor/move2kube-ui:latest
FATA[0000] failed to setup the handlers. Error: "failed to make the workspaces metadata directory at path /move2kube-api/data/metadata/workspaces . Error: \"mkdir /move2kube-api/data/metadata: permission denied\""

Other ideas?

HarikrishnanBalagopal · 2021-09-28T18:01:21Z

@rmarting I tried podman on a RHEL8 VM and it seems to mount without any errors:

$ mkdir data
$ podman run --rm -it -p 8080:8080 -v "${PWD}/data:/move2kube-api/data" quay.io/konveyor/move2kube-ui:latest
INFO[0000] Starting Move2Kube API server at port: 8080

Can you paste the hash of the image that you are using? This is the latest image:

$ podman images | grep ui
quay.io/konveyor/move2kube-ui  latest      08270b4e95e3  12 hours ago  213 MB

You might need to do a podman pull quay.io/konveyor/move2kube-ui to get the latest image.

rmarting · 2021-09-28T18:38:00Z

@HarikrishnanBalagopal I got the same issue in my Fedora 34. I give you some details:

Podman version:

❯ podman version
Version:      3.3.1
API Version:  3.3.1
Go Version:   go1.16.6
Built:        Mon Aug 30 22:46:36 2021
OS/Arch:      linux/amd64

move2kube-ui container image data (as you see the same version):

❯ podman images | grep move2kube-ui
quay.io/konveyor/move2kube-ui                                                               latest                  08270b4e95e3  12 hours ago   213 MB

Which podman version has your RHEL8 VM? Maybe here it is the difference, plus other configuration setup.

HarikrishnanBalagopal · 2021-09-29T07:28:39Z

@rmarting The podman version I used on RHEL8 was 1.9.x . I tried to update it but ran into some issues with dnf and yum.
I have tried podman version 3.3.1 locally on my Macbook Pro with Big Sur.

Can you look through podman images to make sure your image hash starts with 08270b4e95e3 ?
You can also do a podman pull quay.io/konveyor/move2kube-ui and it will pull if there is a newer image.
The full image hash is 08270b4e95e3174209d1f12ae417242c564f294677d3bd989aa7173400a174b3

Also unrelated to this but podman version 3.3.1 has a bug with publishing ports: containers/podman#11396.
It has been fixed and will be released soon in 3.4.0 on Wednesday.

In the meantime the workaround for MacOS users is to either downgrade podman or use --network=bridge

podman run --rm -it -p 8080:8080 --network=bridge quay.io/konveyor/move2kube-ui:latest

rmarting · 2021-09-29T08:16:28Z

@rmarting The podman version I used on RHEL8 was 1.9.x . I tried to update it but ran into some issues with dnf and yum. I have tried podman version 3.3.1 locally on my Macbook Pro with Big Sur.

Can you look through podman images to make sure your image hash starts with 08270b4e95e3 ? You can also do a podman pull quay.io/konveyor/move2kube-ui and it will pull if there is a newer image. The full image hash is 08270b4e95e3174209d1f12ae417242c564f294677d3bd989aa7173400a174b3

As you see in my previous comment my current image already starts with 08270b4e95e3, so it is the same image as you.

Also unrelated to this but podman version 3.3.1 has a bug with publishing ports: containers/podman#11396. It has been fixed and will be released soon in 3.4.0 on Wednesday.

In the meantime the workaround for MacOS users is to either downgrade podman or use --network=bridge
podman run --rm -it -p 8080:8080 --network=bridge quay.io/konveyor/move2kube-ui:latest

Here the issue is related with the volume mounted because my issue occurs only when -v ${PWD}/data:/move2kube-api/data') argument is added.

Is it needed to mount a volume to test locally the tool?

HarikrishnanBalagopal · 2021-09-29T09:54:03Z

As you see in my previous comment my current image already starts with 08270b4e95e3, so it is the same image as you.

Sorry, it's a long line, I didn't notice that you have to scroll right.

Here the issue is related with the volume mounted because my issue occurs only when -v ${PWD}/data:/move2kube-api/data') argument is added.

Can you try with double quotes around ${PWD} ? The PWD path might have spaces in it.

-v "${PWD}/data:/move2kube-api/data"

Is it needed to mount a volume to test locally the tool?

No, you can run it without mounting anything. The mount is just for persistence. Please try without mounting as well.

HarikrishnanBalagopal · 2021-09-29T18:54:33Z

@rmarting I reproduced the issue trying to run the command on a Fedora 34 VM.
Seems to be an issue with namespaces https://ask.fedoraproject.org/t/podman-and-volume-permission-denied/6221

HarikrishnanBalagopal · 2021-09-29T20:02:43Z

@rmarting I was able to get it working by running it in privileged mode

podman run --privileged --rm -it -p 8080:8080 -v "$PWD/data:/move2kube-api/data" quay.io/konveyor/move2kube-ui:latest
INFO[0000] Starting Move2Kube API server at port: 8080

Seems similar to this issue containers/podman#10460 (comment)
and containers/podman#10460 (comment)

ashokponkumar · 2021-09-29T21:21:39Z

For now, let's keep it as a known limitation till podman fixes it for fedora. Let's keep this issue open till then. The workaround is to use the privileged flag only on fedora.

rmarting · 2021-09-30T06:52:16Z

Thanks @HarikrishnanBalagopal to point me to the workaround! It is working right now! I agree to keep this issue still open until confirm that it could be fixed soon by podman. Meanwhile if could be usefull to describe it in the documentation to help others. WDYT?

ashokponkumar · 2021-09-30T17:44:43Z

Agreed @rmarting. Probably we can update in https://move2kube.konveyor.io/installation/web-interface/ (https://github.com/konveyor/move2kube/blob/gh-pages/docs/installation/web-interface.md).

If you get time, please go ahead and create a PR. Or else we will get to it soon.

Thanks for the PRs and updates on adding support for podman in general.

rmarting · 2021-10-01T06:35:21Z

@ashokponkumar I cannot promise something soon, but maybe in a short time I could check/update that reference to add podman as other container engine. I am glad to collaborate.

ashokponkumar · 2021-10-01T06:51:23Z

Thanks @rmarting . Sure. Absolutely. We do understand. Thanks for your collaboration. Glad to have your contributions.

Please do let us know if you have any other suggestions for improvement too.

rmarting · 2021-10-14T16:39:35Z

I found a better way to start locally the container with podman without to use --privilege flag. It is basically adding :z in the mount parameter:

podman run --rm -it -p 8080:8080 -v "$PWD/data:/move2kube-api/data:z" quay.io/konveyor/move2kube-ui:latest

This easy way works smothly and you don't need to use privileged containers. I create a new PR to add these options in the documentation #603. Maybe as soon that PR was merged, this issue could be closed.

ashokponkumar · 2021-10-14T16:50:42Z

I found a better way to start locally the container with podman without to use --privilege flag. It is basically adding :z in the mount parameter:
podman run --rm -it -p 8080:8080 -v "$PWD/data:/move2kube-api/data:z" quay.io/konveyor/move2kube-ui:latest
This easy way works smothly and you don't need to use privileged containers. I create a new PR to add these options in the documentation #603. Maybe as soon that PR was merged, this issue could be closed.

That's a nice find @rmarting! Using --privilege flag was always going to be a red flag, and this solves our problem till podman fixes it for fedora.

ashokponkumar assigned HarikrishnanBalagopal Sep 28, 2021

rmarting mentioned this issue Sep 28, 2021

Use podman as runtime to build and execute the UI konveyor/move2kube-ui#97

Closed

HarikrishnanBalagopal linked a pull request Sep 29, 2021 that will close this issue

chore: update readme with new instructions for UI #595

Merged

ashokponkumar closed this as completed Oct 14, 2021

ashokponkumar assigned rmarting Oct 14, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

UI image does not work with Podman #594

UI image does not work with Podman #594

rmarting commented Sep 28, 2021

ashokponkumar commented Sep 28, 2021

HarikrishnanBalagopal commented Sep 28, 2021 •

edited

Loading

ashokponkumar commented Sep 28, 2021 •

edited

Loading

HarikrishnanBalagopal commented Sep 28, 2021

rmarting commented Sep 28, 2021

rmarting commented Sep 28, 2021

HarikrishnanBalagopal commented Sep 28, 2021 •

edited

Loading

rmarting commented Sep 28, 2021

HarikrishnanBalagopal commented Sep 29, 2021 •

edited

Loading

rmarting commented Sep 29, 2021

HarikrishnanBalagopal commented Sep 29, 2021 •

edited

Loading

HarikrishnanBalagopal commented Sep 29, 2021

HarikrishnanBalagopal commented Sep 29, 2021

ashokponkumar commented Sep 29, 2021

rmarting commented Sep 30, 2021

ashokponkumar commented Sep 30, 2021

rmarting commented Oct 1, 2021

ashokponkumar commented Oct 1, 2021

rmarting commented Oct 14, 2021

ashokponkumar commented Oct 14, 2021

UI image does not work with Podman #594

UI image does not work with Podman #594

Comments

rmarting commented Sep 28, 2021

ashokponkumar commented Sep 28, 2021

HarikrishnanBalagopal commented Sep 28, 2021 • edited Loading

ashokponkumar commented Sep 28, 2021 • edited Loading

HarikrishnanBalagopal commented Sep 28, 2021

rmarting commented Sep 28, 2021

rmarting commented Sep 28, 2021

HarikrishnanBalagopal commented Sep 28, 2021 • edited Loading

rmarting commented Sep 28, 2021

HarikrishnanBalagopal commented Sep 29, 2021 • edited Loading

rmarting commented Sep 29, 2021

HarikrishnanBalagopal commented Sep 29, 2021 • edited Loading

HarikrishnanBalagopal commented Sep 29, 2021

HarikrishnanBalagopal commented Sep 29, 2021

ashokponkumar commented Sep 29, 2021

rmarting commented Sep 30, 2021

ashokponkumar commented Sep 30, 2021

rmarting commented Oct 1, 2021

ashokponkumar commented Oct 1, 2021

rmarting commented Oct 14, 2021

ashokponkumar commented Oct 14, 2021

HarikrishnanBalagopal commented Sep 28, 2021 •

edited

Loading

ashokponkumar commented Sep 28, 2021 •

edited

Loading

HarikrishnanBalagopal commented Sep 28, 2021 •

edited

Loading

HarikrishnanBalagopal commented Sep 29, 2021 •

edited

Loading

HarikrishnanBalagopal commented Sep 29, 2021 •

edited

Loading