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

Publish a ready-to-work docker image #35

Closed
NickVolynkin opened this issue Mar 1, 2023 · 0 comments · Fixed by #36
Closed

Publish a ready-to-work docker image #35

NickVolynkin opened this issue Mar 1, 2023 · 0 comments · Fixed by #36
Assignees

Comments

@NickVolynkin
Copy link
Contributor

NickVolynkin commented Mar 1, 2023

Publish ready-to-work docker image:

  • All dependencies installed (apt, pip)
  • Proof-market-toolchain is precompiled
  • Correct working directory

Currently, users have to compile the project themselves, which takes a lot of time and reduces the success rate.
This image will help new users start working with Proof Market in several minutes.

Also, we will use this image in CI for checking integration between zkLLVM and Proof Market.

Image names:

# build-base image: all dependencies, but no compiled code
ghcr.io/nilfoundation/proof-market-toolchain:base

# ready-to-use image: all dependencies + compiled toolchain applications
ghcr.io/nilfoundation/proof-market-toolchain:latest
NickVolynkin added a commit that referenced this issue Mar 1, 2023
* On builds in the main branch, push image to github registry under name
  ghcr.io/nilfoundation/proof-market-toolchain.
* Use this image as a build base to speed up new image builds.
* Update readme, recommending to pull image rather than build it.

Resolve #35
NickVolynkin added a commit that referenced this issue May 29, 2023
* On builds in the main branch, push image to github registry under name
  ghcr.io/nilfoundation/proof-market-toolchain.
* Use this image as a build base to speed up new image builds.
* Update readme, recommending to pull image rather than build it.

Resolve #35
NickVolynkin added a commit that referenced this issue May 30, 2023
* On builds in the main branch, push image to github registry under name
  ghcr.io/nilfoundation/proof-market-toolchain.
* Use this image as a build base to speed up new image builds.
* Update readme, recommending to pull image rather than build it.

Resolve #35
NickVolynkin added a commit that referenced this issue Jun 2, 2023
* On builds in the main branch, push image to github registry under name
  ghcr.io/nilfoundation/proof-market-toolchain.
* Use this image as a build base to speed up new image builds.
* Update readme, recommending to pull image rather than build it.

Resolve #35
@NickVolynkin NickVolynkin changed the title Push docker image to registry Publish a docker image with compiled proof-market-toolchain Jun 5, 2023
@NickVolynkin NickVolynkin changed the title Publish a docker image with compiled proof-market-toolchain Publish a ready-to-work docker image Jun 5, 2023
@NickVolynkin NickVolynkin self-assigned this Jun 5, 2023
NickVolynkin added a commit that referenced this issue Jun 19, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
NickVolynkin added a commit that referenced this issue Jun 19, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
NickVolynkin added a commit that referenced this issue Jun 19, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
NickVolynkin added a commit that referenced this issue Jun 20, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
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

Successfully merging a pull request may close this issue.

1 participant