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

Problems building act_runner container #250

Closed
dboreham opened this issue Mar 28, 2023 · 10 comments
Closed

Problems building act_runner container #250

dboreham opened this issue Mar 28, 2023 · 10 comments

Comments

@dboreham
Copy link
Collaborator

dboreham commented Mar 28, 2023

Changed title since easier than moving all the comments to a new issue.

@zramsay
Copy link
Collaborator

zramsay commented Mar 29, 2023

running a combo of instructions from the #238 description and https://github.com/cerc-io/stack-orchestrator/blob/main/app/data/stacks/build-support/README.md
worked, with the caveat that #240 was only a partial solution; I had to either modify the stack.yml or mv ~/cerc/act_runner ~/cerc/act-runner

@dboreham
Copy link
Collaborator Author

running a combo of instructions from the #238 description and https://github.com/cerc-io/stack-orchestrator/blob/main/app/data/stacks/build-support/README.md worked, with the caveat that #240 was only a partial solution; I had to either modify the stack.yml or mv ~/cerc/act_runner ~/cerc/act-runner

I think this comment is a different bug. Are you saying that the act-runner container didn't build?

@zramsay
Copy link
Collaborator

zramsay commented Mar 29, 2023

You're right, my comment is ~ tangential to this issue. No, it built fine after I made either one of those tweaks; just needed a logical place to track my hack

@dboreham
Copy link
Collaborator Author

But your hack must mean there's a bug, right?

@dboreham dboreham changed the title Remove forked act_runner Problems building act_runner container Mar 29, 2023
@dboreham
Copy link
Collaborator Author

It shouldn't be necessary to rename the cloned repo, so something is wrong somewhere..

@dboreham
Copy link
Collaborator Author

@zramsay
Copy link
Collaborator

zramsay commented Mar 29, 2023

Right, so this is a case of me being uncertain if it's a) user error, b) incomplete existing documentation, c) undocumented but known bug w/ fix incoming, or d) unknown bug that is now documented.

@dboreham
Copy link
Collaborator Author

Perhaps you had a torn set of commits in your S-O? I think I made two merge commits to fix all the _ vs - stuff.

@zramsay
Copy link
Collaborator

zramsay commented Mar 29, 2023

could very well be, or too much "trying to get something to work" by mucking about in ~/.shiv/laconic-so_BLAH/...

@dboreham
Copy link
Collaborator Author

Closing since this hasn't reoccurred.

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

No branches or pull requests

2 participants