We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm running a docker container with FRR installed. For some reason the watchfrr is always writing to the first shell that is connected.
The issue is that the frrinit.sh start | stop | reload does not work when running from any other shell.
The test was performed on 8.4.4, but I have the same behavior on 10.2.1
docker run -it <img> sh
docker exec -it <container name> sh
Inside the second shell, start the frr service
It does not have to be a shell, using docker run -it <img> top will have the same result.
docker run -it <img> top
when connecting to the second shell all output from watchfrr should go to that shell.
The watchfrr output is printed to the first shell. (on PID 1)
I'm aware that this might be a docker/docker config issue and not an FRR issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
I'm running a docker container with FRR installed. For some reason the watchfrr is always writing to the first shell that is connected.
The issue is that the frrinit.sh start | stop | reload does not work when running from any other shell.
Version
How to reproduce
deploy a container with frr
docker run -it <img> sh
start a new shell
docker exec -it <container name> sh
Inside the second shell, start the frr service
It does not have to be a shell, using
docker run -it <img> top
will have the same result.
Expected behavior
when connecting to the second shell all output from watchfrr should go to that shell.
Actual behavior
The watchfrr output is printed to the first shell. (on PID 1)
Additional context
I'm aware that this might be a docker/docker config issue and not an FRR issue.
Checklist
The text was updated successfully, but these errors were encountered: