-
Notifications
You must be signed in to change notification settings - Fork 0
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
Contract docker #2
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b49e865
feat: dockerfile for contract initialization
MSevey a6c033e
chore(ci): enable contract docker file ci
MSevey cdb40ae
chore(ci): update inputs for dockerfile workflow
MSevey 15d2db9
chore: update rust version and lock in cw-contract version
MSevey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,3 +18,12 @@ jobs: | |
with: | ||
dockerfile: Dockerfile | ||
secrets: inherit | ||
|
||
docker-build-contract: | ||
permissions: | ||
contents: write | ||
packages: write | ||
uses: rollkit/.github/.github/workflows/[email protected] | ||
with: | ||
dockerfile: Dockerfile.contract | ||
secrets: inherit |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# Stage 1: Build the contract using Rust | ||
FROM rust:1.64 as builder | ||
|
||
# Install dependencies | ||
RUN apt-get update && apt-get install -y --no-install-recommends \ | ||
curl \ | ||
git \ | ||
bash \ | ||
build-essential \ | ||
libssl-dev \ | ||
ca-certificates \ | ||
&& apt-get clean && rm -rf /var/lib/apt/lists/* | ||
|
||
# Set up Rust environment and add wasm target | ||
RUN rustup target add wasm32-unknown-unknown | ||
|
||
# Clone the cw-contracts repository | ||
RUN git clone https://github.com/InterWasm/cw-contracts | ||
|
||
# Navigate to the nameservice contract directory | ||
WORKDIR /cw-contracts/contracts/nameservice | ||
|
||
# Compile the contract to wasm | ||
RUN cargo wasm | ||
|
||
# Stage 2: Create a minimal runtime image | ||
FROM alpine:3.20 | ||
|
||
# Install only the necessary runtime dependencies | ||
RUN apk add --no-cache bash curl ranger vim | ||
MSevey marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# Copy the nameservice directory from the builder stage | ||
COPY --from=builder /cw-contracts/contracts/nameservice /root/cw-contracts/contracts/nameservice | ||
|
||
# Keep the container running | ||
CMD tail -F /dev/null | ||
MSevey marked this conversation as resolved.
Show resolved
Hide resolved
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Consider specifying a commit hash or tag for the repository clone.
Cloning the repository without specifying a commit hash or tag can lead to unpredictable builds if the repository changes. Consider specifying a commit hash or tag for reproducible builds.