Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Support the ability to run kantra inside of a single container image #157

Closed
1 task done
dymurray opened this issue Feb 16, 2024 · 4 comments
Closed
1 task done
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@dymurray
Copy link
Contributor

dymurray commented Feb 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

0.3.0

Priority

Major

Current Behavior

Today kantra is expected to run on folks machines and spin up containers to run the analysis engine.

Expected Behavior

It would be really nice if a user could do docker run -v <output_dir>:/tmp/<output_dir> -v <input_dir>:/tmp/<input_dir> quay.io/konveyor/kantra -- analyze --input /tmp/<input_dir> --output /tmp/<output_dir> and have the entire analysis run in a single image.

This would remove the burden on the user significantly.

Anything else?

No response

@dymurray dymurray added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. kind/feature Categorizes issue or PR as related to a new feature. labels Feb 16, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Feb 16, 2024
@djzager djzager removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 16, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Feb 16, 2024
@eemcmullan
Copy link
Collaborator

Closing as decided to not complete

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Planning Mar 8, 2024
@edeandrea
Copy link

Just so its clear - not implementing this requirement requires that a user run/install kantra directly on their machines. There is no option to offer kantra as a container image that someone could then run.

@eemcmullan
Copy link
Collaborator

Was discussing with @dymurray and @pranavgaikwad and we decided on a work-around using analyzer-lsp directly, as a huge percentage of kantra's code is to support how it currently runs (each command in a new container). This means integrating this issue would require a huge re-write. I think an issue or instructions were created for the alternative, but we possibly forgot to share. @dymurray I can't remember if this has been done. If not, I don't mind doing so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: ✅ Done
Development

No branches or pull requests

4 participants