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

Dockerfile: Make more resilient #277

Open
mchack-work opened this issue Oct 17, 2024 · 1 comment
Open

Dockerfile: Make more resilient #277

mchack-work opened this issue Oct 17, 2024 · 1 comment

Comments

@mchack-work
Copy link
Member

mchack-work commented Oct 17, 2024

  • Can we use Alpine or similar small distro as base instead of Ubuntu?

  • We might be able to use more tools directly from distro packages instead of from upstreams. Investigate, for instance, iverilog and verilator.

  • Not very happy with the code patching of nextpnr, even if it's small, in the Dockerfile. Alternatives? Keep a fork of our own of nextpnr? Anything else?

  • Replace at least some of the git clone commands with actual release tar balls. Include digests to see that the downloaded file is what we expected.

@dehanj
Copy link
Member

dehanj commented Oct 17, 2024

Not very happy with the code patching of nextpnr, even if it's small, in the Dockerfile. Alternatives? Keep a fork of our own of nextpnr? Anything else?

I guess the options we have is, in some form of sorted list where 1 is the "best" option:

  1. upstream the changes
  2. figure out if it is really needed, is there any workarounds we can use outside of the specific software?
  3. If the change is small enough: patch in dockerfile
  4. fork the project and maintain

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