-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat(library): Add support for Caddy #12
Conversation
a844725
to
a8d2660
Compare
505c567
to
da99861
Compare
057847e
to
8dd02a3
Compare
0cfedfc
to
2d176d3
Compare
5123081
to
7d3812c
Compare
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.
The README needs to be updated with the build and run commands like the other prs. Everything else works.
7d3812c
to
d8ecab4
Compare
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.
One small comment, all good besides that.
d8ecab4
to
da692bc
Compare
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.
I get this error when running
en1: Interface is up
[ 0.103447] ERR: [libdevfs] Failed to create /dev: 20
[ 0.106231] ERR: [libukboot] Init function at 0x11bfa0 returned error -1
da692bc
to
bf0fde0
Compare
Introduce Caddy 2.7 image (ELF Loader) for bincompat runs. Add `Kraftfile` to build for QMEU and Firecracker on x86_64 using embedded initrd. The current build uses embedded initrd to build a single image consisting of both the kernel and the initial ramdisk. Add GitHub workflow to build and deploy the image. Add success badge in `README.md`. Signed-off-by: Razvan Deaconescu <[email protected]> Co-authored-by: Alexander Jung <[email protected]>
bf0fde0
to
88592be
Compare
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.
All good!
Introduce Caddy bincompat run. Build Caddy as static PIE using a Dockerfile, inspired by Caddy's own Docker setup. Use
xcaddy
to build. The build uses binary compatibility mode (i.e. thebase
image).Add:
Kraftfile
: build / run rules, including pulling thebase
imageDockerfile
: base filesystem, with binary and librariesREADME.md
: document how to useCaddyfile
: Caddy configuration file