github.com/jingruilea/kubeedge@v1.2.0-beta.0.0.20200410162146-4bb8902b3879/docs/troubleshooting/troubleshooting.md (about)

     1  # FAQs
     2  
     3  This page contains a few commonly occuring questions.
     4  For further support please contact us using the [support page](../getting-started/support.md)
     5  
     6  ## Container keeps pending/ terminating
     7  
     8  1. Check the output of `kubectl get nodes`
     9  2. Check the output of `kubectl describe pod <your-pod>`
    10  3. Check the `edgecore` logs for any errors.
    11  4. Check the architecture of the node running `edgecore` and make sure that container image you are trying to run is of the same architecture.
    12     For example, if you are running `edgecore` on Raspberry Pi 4, which is of `arm64v8` architecture, the nginx image to be executed would be `arm64v8/nginx` from the docker hub.
    13  
    14  5. Also, check that the `podSandboxImage` is correctly set as defined in [Modification in edgecore.yaml](https://github.com/kubeedge/kubeedge/blob/master/docs/setup/kubeedge_configure.md#modification-in-edgecoreyaml).
    15  
    16  6. If all of the above is correctly set, login manually to your edge node and run your docker image manually by
    17  
    18     ```shell
    19      docker run <your-container-image>
    20     ```
    21  
    22  7. If the docker container image is not pulled from the docker hub, please check that there is enough space on the edge node.
    23  
    24  ## Where do we find cloudcore/edgecore logs
    25  
    26  This depends on the how cloudcore/ edgecore has been executed.
    27  
    28  1. If `systemd` was used to start the cloudcore/ edgecore? then use `journalctl --unit <name of the service probably edgecore.service>` to view the logs.
    29  2. If `nohup` was used to start the cloudcore/ edgecore, either a path would have been added where the log is located, Otherwise, if the log file wasn't provided, the logs would be written to stdout.
    30  
    31  ## Where do we find the pod logs
    32  
    33  Connect to the edge node and then either
    34  
    35  - use the log file located in `/var/log/pods` or
    36  - use commands like `docker logs <container id>`
    37  
    38  **kubectl logs** is not yet supported by KubeEdge.