feat(examples): Add Caddy example #14
Closed
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
razvand
force-pushed
the
razvand/examples/caddy-2.7
branch
6 times, most recently
from
b8eeda8 to
48accd4
Compare
Add script to start and setup the BuildKit container. This is required for Dockerfile root filesystems present in the Kraftfile. Signed-off-by: Razvan Deaconescu <[email protected]>
…uildkit feat(utils): Add script to start BuildKit container Reviewed-by: Stefan Jumarea <[email protected]> Approved-by: Stefan Jumarea <[email protected]>
Currently the `utils/start-buildkitd.sh` was starting the BuildKit container if the container didn't exist. It didn't start it in case it was stopped. This commit fixes this, by looking if the container exists and then starting it. Signed-off-by: Razvan Deaconescu <[email protected]>
…ildkitd fix(utils): Start BuildKit container if it was stopped Reviewed-by: Mihnea Firoiu <[email protected]> Approved-by: Stefan Jumarea <[email protected]>
Update `Kraftfile` configuration for `base` to use `staging` branches for all repositories (`unikraft`, `app-elfloader`, `lwip`, `libelf`). Signed-off-by: Razvan Deaconescu <[email protected]>
…uildkit feat(utils): Add script to start BuildKit container Reviewed-by: Stefan Jumarea <[email protected]> Approved-by: Stefan Jumarea <[email protected]>
Add script that builds all variants of base kernels, i.e. ELF Loader app images: QEMU / Firecracker, simple / strace-printing / debug-printing. Kernels are outputed in the `kernels/` top-level directory to be linked in application directories. Signed-off-by: Razvan Deaconescu <[email protected]>
razvand
force-pushed
the
razvand/examples/caddy-2.7
branch
from
48accd4 to
af75214
Compare
Introduce Python script to generate run scripts for bincompat use cases. Add base `docker.Makefile` to be included for Docker-based builds. Script is to be run from corresponding bincompat app directory in examples: ``` ../../utils/bincompat/generate.py ``` Application directories must define the `config.yaml` file with required variables: `networking`, `accel`, `memory` etc. Running it generates the following files: * `kraft-run*.sh`: script to run with KraftKit * `run-qemu*.sh`: script to run with QEMU * `run-fc*.sh`: script to run with Firecracker * `fc*.json`: Firecracker configuration files Signed-off-by: Razvan Deaconescu <[email protected]>
feat(utils): Introduce bincompat generator script Reviewed-by: Mihnea Firoiu <[email protected]> Approved-by: Stefan Jumarea <[email protected]>
Add `README.maintainers.md`. This contains common instruction for setting up, configuring, building, running, using and testing applications stored in subdirectories. Specific instructions are to be handled by individual `README.md` file in each application / example subdirectory. Currently, instructions are used for binary compatible (bincompat) applications. Signed-off-by: Razvan Deaconescu <[email protected]>
…readme feat(readme): Add README for maintainers Reviewed-by: Mihnea Firoiu <[email protected]> Approved-by: Stefan Jumarea <[email protected]>
Introduce Caddy as binary compatibility run. Build Caddy as static PIE application using `Dockerfile`. Then run it with the `base` kernel images from `../../kernels/`. Add typical files for a bincompat app: * `Kraftfile`: build / run rules, including pulling the `base` image * `Dockerfile`: filesystem, including binary and libraries * `Makefile`: used to generate the root filesystem from the `Dockerfile` rules * `README.md`: instructions to set up, build and run the application * `config.yaml`: configuration file to generate scripts to the application * `hosts`, `Caddyfile`: required Caddy configuration files `config.yaml` is used to generate run scripts using the `../../utils/bincompat/generate.py` script. The kernels in `../../kernels` are generated by running the `../../utils/bincompat/base-build-all.sh` script while inside the `../../library/base/` directory. Signed-off-by: Razvan Deaconescu <[email protected]>
razvand
force-pushed
the
razvand/examples/caddy-2.7
branch
from
af75214 to
fe9892b
Compare
|
This was solved by #93 |
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.
Add example for Caddy. It pulls and runs the Caddy Unikraft runtime from the registry. Custom configuration and files can be added to the
data/directory.