haproxy-certbot container restart loop

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose, dockerfile, shell

Research direction

Start with haproxy-certbot/docker/start.sh at line 52 and reproduce the failure using docker-start-services.sh with the documented Docker Compose setup for ThingsBoard 3.3.4.1 on Fedora 36. Inspect the iptables error and verify the container no longer enters a restart loop under the reported setup.

Written by the indexing model from the issue text.

Description

When running the haproxy-certbot container (via docker-compose or otherwise), it does not start properly and instead enters a restart loop. This is all following these docs for version 3.3.4.1 on Fedora 36.

haproxy-certbot container logs from running using docker-start-services.sh from the Thingsboard repo:

iptables v1.8.4 (legacy): unknown option "--set-mark"
Try `iptables -h' or 'iptables --help' for more information.

Here is the line from the start.sh script that seems to be causing the issue:
https://github.com/thingsboard/docker/blob/9712b3d5f93be445f51c8fccedfeee3be15f63e7/haproxy-certbot/docker/start.sh#L52

Dominant language
Dockerfile
Stars
8
Forks
20
Avg merge
6m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from thingsboard/docker

All issues in thingsboard/docker

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.