-
Notifications
You must be signed in to change notification settings - Fork 3
Installation improvements. #11
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
Conversation
install.sh
Outdated
| function make_executable() { | ||
| go build -o $executable | ||
| go build -o $executable \ | ||
| || podman run --rm -v "$PWD:/workdir:Z" -w "/workdir" golang:1 go build -o $executable \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| || podman run --rm -v "$PWD:/workdir:Z" -w "/workdir" golang:1 go build -o $executable \ | |
| || podman run --rm -v "$PWD:/workdir" -w "/workdir" golang:1 go build -o $executable \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not been able to test elsewhere, but on my machine selinux is enabled (fedora based), and without the context parameter (the Z) the container is not able to access the files that is mounted. To work around this I suppose I could setup a volume, copy the files into that volume, build, then copy the binary back out of the volume after, but it seems easier to just mount the path.
|
Thank you for the contribution! I have some nitpicks, otherwise, LGTM. |
|
Additionally, please update the README.md file in the requirements section. |
|
Thank you for the contribution |
Small changes to the installation script to expand the possibilities of installation working well for more users.