---
title: "The PTP4L container on the VXs Host keeps Rebooting"
slug: "the-ptp4l-container-on-the-vxs-host-keeps-rebooting"
updated: 2024-12-19T06:52:03Z
published: 2024-12-19T06:52:03Z
canonical: "docs.telosalliance.com/the-ptp4l-container-on-the-vxs-host-keeps-rebooting"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The PTP4L container on the VXs Host keeps Rebooting

## SCOPE

This applies to the PTP4L container for the VXs system running on a Linux host only.

## DESCRIPTION

Sometimes after installation, you might find that the ptp4l container crashes and reboots constantly. You'll know this is happening if you type `sudo docker ps -a` into your host's command line and see this next to your ptp4l container:

```plaintext
STATUS
Restarting (0) 23 seconds ago
```

Usually, this will happen because there is no Ethernet interface bound to the container. The remedy is pretty simple.

1. First, determine the Ethernet interface being used for AoIP using `ifconfig`
2. Once you determine the correct interface, make note of its name and add it to the `PTP4L_ARGS` line of the `.env` file in your ptp4l configuration directory located at `/opt/telos` with the parameter `-i` like this:

```plaintext
root@host:/opt/telos/ptp4l# cat .env
TAG=
PTP4L_ARGS= -i eno2
```

> [!WARNING]
> Note that you'll need to use Vim, Nano, or your favorite text editor to make this change.

1. Shut down the container using `sudo docker-compose down` from your ptp4l configuration directory
2. Turn the container back up using `sudo docker-compose up -d` from your ptp4l configuration directory.

Check that the container is now successfully running using `sudo docker ps -a` :

```plaintext
STATUS
Up 30 seconds
```

## Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please [contact us](https://www.telosalliance.com/support-request).