Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Attachments
Issue Links
Activity
| Description |
After Ansible deplyment, there are some cases where the Docker containers have no internet access (such as It would be ideal if we could check this case automatically. |
After Ansible deplyment, there are some cases where the Docker containers have no internet access (such as It would be ideal if we could check this case automatically. |
| Summary | Check container internet access after Ansible deplyment | Check container internet access after Ansible deployment |
| Description |
After Ansible deplyment, there are some cases where the Docker containers have no internet access (such as It would be ideal if we could check this case automatically. |
After Ansible deployment, there are some cases where the Docker containers have no internet access (such as It would be ideal if we could check this case automatically. |
| Component/s | Buildbot [ 18503 ] | |
| Labels | buildbot |
| Labels | re-evaluate |
| Workflow | MariaDB v4 [ 163039 ] | MariaDB Foundation v1 [ 188144 ] |
| Rank | Ranked lower |
| Status | Open [ 1 ] | Needs Feedback [ 10501 ] |
| Labels | re-evaluate | foundation re-evaluate |
| Assignee | Faustin Lammler [ faust ] |
This has not been seen for a while, we normally use ufw with Docker and it does not need any other tunning.
| Status | Needs Feedback [ 10501 ] | Open [ 1 ] |
| Fix Version/s | N/A [ 27305 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Remaining Estimate | 0d [ 0 ] |
If you can show me how to reproduce this, I can maybe try to understand what is the error in ansible deployment. There might be an order in the docker daemon starting phase that needs to be respected (and yes, this is probably docker playing with iptables and adding it's NAT rules). I don't see where Ansible could be responsible but we can surely improve this.