SSH and HTTP Server with C and Debugging Tools
This guide explains how to create and deploy a C app with debugging enabled. To run this example, follow these steps:
- Install the CLI. Use the unikraft CLI or the legacy kraft CLI. You need a BuildKit builder. The easiest way to get one is via Docker. Alternatively, you can also directly set up and use BuildKit, see the quick start.
The unikraft CLI is the current standard, while kraft is the legacy version. Choose one of the CLIs below and only run the commands associated with it for the rest of this guide.
- Clone the
examplesrepository andcdinto theexamples/httpserver-c-debugdirectory:
Code
Make sure to log into Unikraft Cloud and pick a metro close to you.
This guide uses fra (Frankfurt, 🇩🇪):
For extensive debug information with strace, add the USE_STRACE=1 environment variable to the deploy command:
The output shows the instance address and other details:
In this case, the instance name is httpserver-c-debug-5pvem and the address is patient-snow-zdzhdy8r.fra.unikraft.app.
They're different for each run.
Use curl to query the Unikraft Cloud instance:
Code
Code
For SSH, you need to set up a tunnel that handles the TLS connection to the Unikraft Cloud instance. This way, you have a non-TLS port that your SSH client can connect to:
Code
Then connect to the instance via SSH using:
Code
You might see warnings like REMOTE HOST IDENTIFICATION HAS CHANGED.
This is normal if you have set up tunnels to connect with SSH on localhost, so don't worry.
You can list information about the instance by running:
When done, you can remove the instance:
Learn more
Use the --help option for detailed information on using Unikraft Cloud:
Or visit the CLI Reference or the legacy CLI Reference.