10. Troubleshooting and Known Issues
Hint
Abstract
This chapter collects the switches which show what a pilot is doing and the issues which are known to get in the way.
10.1. Debugging a Flake
Both pilots report the details of their work if the following environment variable is set:
PILOT_DEBUG=1 myapp
The output shows which flake configuration was read, which engine command was constructed from it and, for VM applications, which kernel commandline and which TAP device name the instance is started with. This is the first thing to look at whenever an application does not behave as expected.
10.2. Known Issues
10.2.1. selinux
The security profiles of selinux often prevents operations done by the pilots. In case of trouble and to check if selinux might be the cause, try to temporarily disable selinux as follows:
sudo setenforce 0
For container based flakes, the selinux context of the container
image might also be the cause of problems. In this case, try to run
the container with the --security-opt label=disable option. This
can be done by passing the following option to the flake registration
command:
--opt "\--security-opt label=disable"
10.3. Feedback
Feedback is very much welcome. Please report issues and improvements at: