docs: quickstart guide #104
Merged
Conversation
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
I tried to connect different pieces together and see what do we need to run reignite. Steps I described: * Set up a tap device forwarded through the default internet device. * Create thinpool * Configure containerd * Start and access containerd * Start firecracker * Start reignite * One case on troubleshooting (`failed to reconcile vmid`) The whole setup tries to make it a well separated environment, where all containerd resources (thinpool, socket, meta, etc.) are living under `/var/lib/containerd-dev`, that way we can easily avoide conflicts with containerd for docker or other tools.
Codecov Report
@@ Coverage Diff @@
## main #104 +/- ##
=======================================
Coverage 67.41% 67.41%
=======================================
Files 23 23
Lines 758 758
=======================================
Hits 511 511
Misses 184 184
Partials 63 63 Continue to review full report at Codecov.
|
* Use macvtap devices instead of tap devices. * Change metadata volume to 10G from 2G. * Instructions how to compile or download custom built Firecracker from Discussion#107 * Remove `plugins."io.containerd.grpc.v1.cri".containerd`. * Recommended debug level `trace` for containerd. * Remove `--firecracker-api` flag as it defaults to true. * Change `--parent-iface` to the macvtap device. References: * liquidmetal-dev#107 (comment)
It did not work because:
2021/10/05 11:49:32 failed to unmount /run/user/1000/containerd-mount2008466432:
operation not permitted:
failed to mount /run/user/1000/containerd-mount2008466432:
operation not permitted
exit status 1
I assume it can be solved easily, but I don't have patience to figure it
out.
richardcase
reviewed
Oct 5, 2021
yitsushi
added a commit
to yitsushi/flintlock
that referenced
this pull request
Oct 5, 2021
* Remove the "Set up networking" section [1] * Extract `devpool.sh` out into `hack/scripts/devpool.sh` [1]: liquidmetal-dev#104 (comment)
* Remove the "Set up networking" section [1] * Extract `devpool.sh` out into `hack/scripts/devpool.sh` [1]: liquidmetal-dev#104 (comment)
yitsushi
force-pushed
the
quickstart-guide
branch
from
bacb111 to
864e008
Compare
|
@richardcase : What can I do to make the title checker happy? Update: change the title and restarted the job, it's in the queue. Changing the title a bit did not help. |
|
@yitsushi The error on the check is
I found the reason for this here: actions/first-interaction#10 (comment). It seems like you (and probably me) don't have the correct repo permissions to access a certain resource (most likely the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
I tried to connect different pieces together and see what do we need to
run reignite.
Steps I described:
failed to reconcile vmid)The whole setup tries to make it a well separated environment, where
all containerd resources (thinpool, socket, meta, etc.) are living under
/var/lib/containerd-dev, that way we can easily avoide conflicts withcontainerd for docker or other tools.
Special notes for your reviewer:
For now, this document can be useful to engineers to set up their local environment.
Missing parts:
Checklist:
Release note: