mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-25 16:45:53 +03:00
[GH-ISSUE #516] Building fails in mono Docker container #470
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#470
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @keeferrourke on GitHub (Jul 19, 2018).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/516
After building
nbfcfailed due to claims of missing assembly references on my Fedora 28 Workstation laptop (Lenovo Yoga 710-15ISK), even after installing the mono runtime as suggested in the Wiki (instead of using the packaged runtime), I figured that building from within the Docker container would be the next best thing.Turns out that building within
mono:latesthas the same issues. Note that I had issues with permissions mounting this repo's source code as a docker volume (the build script complained about being unable to access thepackagesdirectory), and ended up cloning this repo directly into the container at/opt/nbfcinstead.Log output below:
And since the Assembly references were still an issue, I checked out version
1.5.0and got these errors instead...How can I build this thing on Linux?
@mfdewit commented on GitHub (Oct 22, 2018):
I had the same error. On my machine this was caused by the wget binary not being present inside the docker container. After installing it (apt update && apt install wget), the error was gone.
@JimboJoe commented on GitHub (Nov 24, 2018):
That did the trick for me, thanks (that should ideally be added to the wiki)!
@github-actions[bot] commented on GitHub (Nov 25, 2019):
This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed