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

./kuboreleaser env via docker does not seem to work #40

Closed
lidel opened this issue Aug 21, 2024 · 1 comment
Closed

./kuboreleaser env via docker does not seem to work #40

lidel opened this issue Aug 21, 2024 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@lidel
Copy link
Member

lidel commented Aug 21, 2024

If .env is missing, there is a problem fixed in #39

If .env exists, there is this error:

./kuboreleaser env                                                                                                                                                                                                                                               ...ipfs/kuboreleaser main
INFO[2024-08-21 23:11:44] Checking the status of the action...
INFO[2024-08-21 23:11:44] The action is not complete yet, continuing...
WARN[2024-08-21 23:11:44] file .env does not exist yet in the current directory (the action is not complete)
INFO[2024-08-21 23:11:44] Running the action...
FATA[2024-08-21 23:11:44] fork/exec /tmp/.env.1321094857.sh: text file busy

cc @galargh ipfs/kubo#10436

@lidel lidel added the kind/bug A bug in existing code (including security flaws) label Aug 21, 2024
lidel added a commit that referenced this issue Aug 28, 2024
@lidel lidel closed this as completed in a0746c2 Aug 28, 2024
@galargh
Copy link
Contributor

galargh commented Aug 30, 2024

Hey! I just got to it, thank you for spotting and fixing it - much appreciated 🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

No branches or pull requests

2 participants