Uptime Monitoring
-
This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron.
I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.
I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.
Any help would greatly be appreciated!
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase See 'docker build --help'. node:child_process:903 throw err; ^ Error: Command failed: docker build -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile /Users/michael/Downloads/cloudron-uptime-kuma-app at checkExecSyncError (node:child_process:826:11) at execSync (node:child_process:900:15) at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5) at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9) at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31) at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14) at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18) at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12) at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10) at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) { status: 125, signal: null, output: [ null, null, null ], pid: 9877, stdout: null, stderr: null }@mazarian Oh weird... not sure why its just default trying to use my docker registry... O_O
Any docker wizards here who might have some insight?
-
This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron.
I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.
I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.
Any help would greatly be appreciated!
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase See 'docker build --help'. node:child_process:903 throw err; ^ Error: Command failed: docker build -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile /Users/michael/Downloads/cloudron-uptime-kuma-app at checkExecSyncError (node:child_process:826:11) at execSync (node:child_process:900:15) at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5) at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9) at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31) at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14) at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18) at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12) at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10) at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) { status: 125, signal: null, output: [ null, null, null ], pid: 9877, stdout: null, stderr: null }@mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use
cloudron build. I went "the long way".docker build -t <myrepo>/<appname>:<tag> . docker push <myrepo>/<appname>:<tag> cloudron install --image <myrepo>/<appname>:<tag>NB the trailing dot on 1st line
With this the build/install was seamless
Kuma now working brilliantly and I have deleted my UptimeRobot account.thanks again @atridad
-
@mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use
cloudron build. I went "the long way".docker build -t <myrepo>/<appname>:<tag> . docker push <myrepo>/<appname>:<tag> cloudron install --image <myrepo>/<appname>:<tag>NB the trailing dot on 1st line
With this the build/install was seamless
Kuma now working brilliantly and I have deleted my UptimeRobot account.thanks again @atridad
@timconsidine Perhaps I should change my instructions? @staff does the cloudron build command do some extra stuff that would be causing this?
-
@mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use
cloudron build. I went "the long way".docker build -t <myrepo>/<appname>:<tag> . docker push <myrepo>/<appname>:<tag> cloudron install --image <myrepo>/<appname>:<tag>NB the trailing dot on 1st line
With this the build/install was seamless
Kuma now working brilliantly and I have deleted my UptimeRobot account.thanks again @atridad
-
@timconsidine Thanks for this! I'm not sure how much of my issue had to do with my Mac environment but I was able to get it all setup using Ubuntu using your method and it worked like a charm!
-
@timconsidine Perhaps I should change my instructions? @staff does the cloudron build command do some extra stuff that would be causing this?
@atridad said in Uptime Monitoring:
@timconsidine Perhaps I should change my instructions?
errr, I'm not qualified on that !
I blunder about, find what works for me and tend to stick to that. -
@atridad said in Uptime Monitoring:
@timconsidine Perhaps I should change my instructions?
errr, I'm not qualified on that !
I blunder about, find what works for me and tend to stick to that.@timconsidine lol with packaging I'm the same way tbh. Cloudron was my first time editing or making a Dockerfile
-
This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron.
I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.
I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.
Any help would greatly be appreciated!
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase See 'docker build --help'. node:child_process:903 throw err; ^ Error: Command failed: docker build -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile /Users/michael/Downloads/cloudron-uptime-kuma-app at checkExecSyncError (node:child_process:826:11) at execSync (node:child_process:900:15) at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5) at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9) at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31) at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14) at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18) at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12) at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10) at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) { status: 125, signal: null, output: [ null, null, null ], pid: 9877, stdout: null, stderr: null }@mazarian said in Uptime Monitoring:
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
I think this happenned because the docker repository was specified incorrectly when you did
cloudron build. You can alwayscloudron build --set-repositoryagain and it will ask you again for the repository name. The repo name should likegirish/cloudron-uptime-kumaor something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images. -
@mazarian said in Uptime Monitoring:
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
I think this happenned because the docker repository was specified incorrectly when you did
cloudron build. You can alwayscloudron build --set-repositoryagain and it will ask you again for the repository name. The repo name should likegirish/cloudron-uptime-kumaor something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images. -
@mazarian said in Uptime Monitoring:
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
I think this happenned because the docker repository was specified incorrectly when you did
cloudron build. You can alwayscloudron build --set-repositoryagain and it will ask you again for the repository name. The repo name should likegirish/cloudron-uptime-kumaor something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images.
