Upgrade to Caddy docker image 1.X

[cliftonmcintosh]

We are currently using the Caddy docker image 0.11.5. The most recent version of the Caddy docker image is 1.0.3. An attempt to run 1.0.3 on beta.nepalmap.org suggests there may be some adjustment that needs to be made in order to run 1.X.

This is what the error looks like when the caddy server tries to start

caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
nepalmapfederal_caddy_1 exited with code 1

[cliftonmcintosh]

@suvash

Would you be willing to work on this upgrade (or even an upgrade to Caddy 2)? If so, we can provide you with a test server from which to test, if needed.

[suvash]

Hi ! Sure, I can look into upgrading to Caddy 2. Though, probably sometime in Jan. Does that sound reasonable ?

[suvash]

I just remembered this. I'm def. a bit more free now. How do we go about this ? If you've already done parts of it, or what you had in mind ?

[cliftonmcintosh]

@suvash

Thank you. No one has done any parts of this.

[suvash]

@cliftonmcintosh I spend some time today upgrading caddy to v2. A couple of changes and it worked fine. But, it seems like the django app is broken in master. make start on APP_ENV=dev (on dev branch) doesn't seem to start the app properly, lots of failures in db bootstrap, and the web app fails on web requests. Is anybody working on this, or any pointers ? or, should I work from another branch instead ?

[suvash]

So, I finally was able to make Caddy v2 work on a branch based of master, more details here https://github.com/Code4Nepal/nepalmap_federal/pull/112

We can continue the conv. there. Please feel free to close this issue.