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

Unable to build ood image from docker file #3625

Open
vikaspatil02 opened this issue Jun 24, 2024 · 5 comments
Open

Unable to build ood image from docker file #3625

vikaspatil02 opened this issue Jun 24, 2024 · 5 comments
Milestone

Comments

@vikaspatil02
Copy link

image Build is failing in step --> rake -f /opt/ood/Rakefile -mj$CONCURRENCY build
[root@cc4ca5118686 ood]# rake -f /opt/ood/Rakefile -mj$CONCURRENCY build
shellcheck -x ood-portal-generator/sbin/update_ood_portal
cd /opt/ood/ood-portal-generator
rake aborted!
Command failed with status (127): [shellcheck -x ood-portal-generator/sbin/update_ood_portal]
/opt/ood/lib/tasks/test.rb:53:in block (2 levels) in <top (required)>' /usr/local/share/gems/gems/rake-13.2.1/exe/rake:27:in <top (required)>'
Tasks: TOP => default => test => test:all => test:shellcheck

@osc-bot osc-bot added this to the Backlog milestone Jun 24, 2024
@johrstrom
Copy link
Contributor

Thanks, this container doesn't really get updated as it's not really meant for production use.

Seems like it should actually install the latest stable version from a package. @treydock do you have thoughts here? I'm a bit torn. If we remove it, we'll get questions on how to build it and the answer is you kind of don't want to. But if they do really want to, then we need to maintain an actual stable Dockerfile that would work.

@treydock
Copy link
Contributor

The Dockerfile.dev is closest to "production" install of OnDemand but still not something I'd recommend for production as it's only intended for developers of OnDemand. OnDemand itself isn't really designed to run from a container but it should be possible. I'll see if I can throw something together, but it will be mostly untested.

@johrstrom
Copy link
Contributor

Yea we just updated a ticket somewhere here to update the Dockerfile. Seems like it should just install the latest RPM (something we'll have to update as we make releases) and call it a day.

@treydock
Copy link
Contributor

What I'm doing is just leaving that Dockerfile, though we may want to remove it if we use Dockerfile.dev and Dockerfile is unused. I'm creating packaging/container/Dockerfile for the packaged container

@johrstrom
Copy link
Contributor

Sure. If you're working on it, then yea, remove that Dockerfile at the root of the project if there'll be another - or symlink it so that folks can see it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants