Running chisel server in a docker container does not seem to re-read the authfile
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
When chisel is started in a container, it reads the authfile on startup, but does not seem to notice when the file is modified if it is mounted using a -v option:
#!/bin/bash
export CHISEL_LE_EMAIL=some@email.addr
docker run --net=host --name chisel --restart always \
--log-opt max-size=10m --log-opt max-file=2 \
-d -e PORT=443 -v /home/MYUSER/chisel:/chisel jpillora/chisel server \
--authfile /chisel/users.json \
--backend https://some.other.server \
--reverse --tls-domain this.server --pid -v
This works really well as a chisel server, and restarts on server restart etc. However, if the users.json file in /home/MYUSER/chisel/users.json is updated, the server does not notice and re-read the file.
Is there some further configuration that is needed?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the chisel server entry point and the mounted /chisel/users.json authfile described in the report. Reproduce the Docker bind-mount setup, update users.json while the server runs, and determine whether the server reloads it; done means updated authentication takes effect or the required configuration is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100