docs(deployment): add note about potential firewall issues on RHEL (#2707)
Add a warning box to the troubleshooting advice (https://docs.browsertrix.com/deploy/local/#debugging-pod-issues) in the local deployment guide about firewall rules and disabling firewalld on RHEL. See https://forum.webrecorder.net/t/browsertrix-deployment-stalls-when-initializing-container-migrations/916/5 for context.
This commit is contained in:
parent
7a6b1d7e73
commit
80a225c677
@ -180,11 +180,16 @@ There should be 4 pods listed: backend, frontend, minio, and mongodb. If any one
|
||||
|
||||
To get more details about why a pod has not started, run `#!sh kubectl describe <podname>` and see the latest status at the bottom.
|
||||
|
||||
Often, the error may be obvious, such as failed to pull an image.
|
||||
Often, the error may be obvious, such as "failed to pull an image."
|
||||
|
||||
If the pod is running, or previously ran, you can also get the logs from the container by running `#!sh kubectl logs <podname>`
|
||||
If the pod is running, or previously ran, you can also get the logs from the container by running `#!sh kubectl logs <podname>`.
|
||||
|
||||
The outputs of these commands are helpful when reporting an issue [on GitHub](https://github.com/webrecorder/browsertrix/issues)
|
||||
The outputs of these commands are helpful when reporting an issue [on GitHub](https://github.com/webrecorder/browsertrix/issues).
|
||||
|
||||
??? info "Firewall rules (on RHEL/Fedora)"
|
||||
|
||||
On Red Hat Enterprise Linux and derivatives, communication between pods might be blocked by firewalld.
|
||||
There are short guides on configuring the firewall for these systems in the [k3s](https://docs.k3s.io/installation/requirements?&os=rhel#operating-systems) and [Microk8s](https://microk8s.io/docs/troubleshooting#:~:text=Pod%20communication%20problems%20when%20using%20firewall-cmd) documentation.
|
||||
|
||||
## Updating the Cluster
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user