How do I do this??

[scooke]

Very unclear topic title, I know. Sorry.

I'm trying to use some custom apps. I've been able to install at least one, paperless-ng, but I can't find my own notes about how I did it. I have it running on my Cloudron. Now, I'm trying to tackle some others, like @nj's cloudron-keycloak and cloudron-outline. @nj has kindly listed some steps in their github repository, but for someone like me there seem to be steps missing that don't make sense!

Here is what I think I need to do (using the steps listed plus my own):

In my Ubuntu VM on Windows, I've clone the respository: git clone https://github.com/njsubedi/cloudron-keycloak.git

I've then logged into my new Docker Registry on my Cloudron: docker login docker.example.com, and it worked.

I'm also logged into my Cloudron using the cli on the Ubuntu VM

I've cd'ed into the clone repository on my Ubuntu VM: cd cloudron-keycloak

Here is where I falter.

Do I cloudron build first? Because the instructions say this builds AND publishes the image. But, I haven't set any details yet about publishing anything.

The next step is to name the image: docker.example.com/me/cloudron-outline (I've reworded it to make more sense for myself), but, does me use the name that I used to login to docker.example.com, my Cloudron Docker Registry, or do I need to make this user or directory?? Or is this not going to be njsubedi by default since I'm working on their image that I cloned? Do I need to clone this on Github to my own Github account before cloning it? But, my Github username is not the same as my docker.example.com Registry user name, so the same question still exists - where does that name me come from?

Then instructions then say to: Install the app cloudron install -l <auth.yourdomain.tld>, but does this mean, I cd into the cloned directory on my Ubuntu VM, which has had the command cloudron build run on it already, and somehow the cloudron install command knows what docker image to use? So I just run cloudron install -l new.domain.tld and the app will get installed?

IF SO, then at what point do I push all this my Cloudron's Docker registry??? After the clone? Before the Build? After the Build? After the Install? And, regardless of the answer to that, once I've pushed the image to my own Docker repository... what's the point? It seems like all the work is done on the Ubuntu VM, in the cloned repository. And to then update... I need to pull from @nj's original Github repository, right?? To anyone brave enough to try to help me, thank you.

I hope my confusion is clear! I'm asking all this before doing anything else other than the initial clone from @nj's Github repository so that I understand it all well and can avoid missing some crucial step.

[BrutalBirdie]

@scooke

I will try to make it very short and understandable
Example from Greenlight => https://git.cloudron.io/cloudron/greenlight-app

git clone ssh://git@git.cloudron.io:6000/cloudron/greenlight-app.git
cd greenlight-app
docker build --file Dockerfile --target dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20 .
docker push dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20

Now if you view your Cloudron Docker Registry you should see your pushed docker image.

In this screenshot you can see docker images build by cloudron build by the cloudron build service with automated tags, that's why they seem a bit cryptic.

Now make sure you have setup your docker registry to be used in your Cloudron Server.
https://my.domain.tld/#/settings => Private Docker Registry

Now you should be able to install:

cloudron install --location test --image dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20

App is being installed.

 => Queued
 => Registering subdomains
 => Registering location: test.cloudron.dev.......
 => Downloading image ..
 => Creating container
 => Waiting for DNS propagation ...
 => Wait for health check .......................

App is installed.

Cheers

---

Explaining some stuff you asked.

IF SO, then at what point do I push all this my Cloudron's Docker registry??? After the clone? Before the Build? After the Build? After the Install? And, regardless of the answer to that, once I've pushed the image to my own Docker repository... what's the point? It seems like all the work is done on the Ubuntu VM, in the cloned repository. And to then update... I need to pull from @nj's original Github repository, right?? To anyone brave enough to try to help me, thank you.

I hope my confusion is clear! I'm asking all this before doing anything else other than the initial clone from @nj's Github repository so that I understand it all well and can avoid missing some crucial step

You cant push / publish anything if you don't build it first.

what's the point

well.. your cloudron server can't just download the docker image from your local computer.

[scooke]

@BrutalBirdie Thank you, this is really helpful, and I think I've followed it all. I would have left out the --file and --target options in the build step, for example.

A few questions to help me grasp the concepts...

Building something to have something to push, pull makes sense. After I've built, and pushed, what happens to the original directory which I built in? Can I delete it?

If I do delete it, how does that image get updated? Don't I have to re-clone, re-build, re-push, making the first image useless (and every subsequent one after each update).

If I don't delete it, this means it is an essential directory that I basically will never delete, right? And over time it will get quite large as I pull or clone updates to it?

For the install, cloudron install --location test --image dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20 can be run anywhere local then, right? It doesn't need to be in that original clone/build directory because I've previously logged in to both my Cloudron and my self-hosted Docker Registry and the --options are used by cloudron install to know where these things are, right?

As for the final "point" question... must I push the built image somewhere? Can't it/doesn't it just stay in the clone directory (I'm assuming that's where the Docker image is after I've run "build")? If I can just leave it, then the install command would have to locate it, cloudron install --location test --image C://Users/me/cloudron/org.bigbluebutton.greenlight.cloudronapp:1.0.20, something like that, right? So if I can just leave it where it is, this whole Docker Registry thing is just a way to nicely keep built images organized, yes? And I guess for something like Docker Hub, able to share any images.

[timconsidine]

@scooke said in How do I do this??:

For the install, cloudron install --location test --image dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20 can be run anywhere local then, right? It doesn't need to be in that original clone/build directory because I've previously logged in to both my Cloudron and my self-hosted Docker Registry and the --options are used by cloudron install to know where these things are, right?

I think it needs to be run from inside the directory where you have CloudronManifest.json.

[scooke]

Welp, I've had the first error, the exact type that has made Docker seem like some super bizarre esoteric only-true-devs-can-use-it, the very first time I've tried to follow @BrutalBirdie's instructions.

I've run this:

me@vm:~/cloudron/cloudron-odoo$ docker build --file Dockerfile --target docker.toutdo.com/org.odoo.cloudronapp:1.0.20 .
[+] Building 0.3s (2/2) FINISHED
 => [internal] load build definition from Dockerfile                                                                                                                                                                                   0.1s
 => => transferring dockerfile: 1.95kB                                                                                                                                                                                                 0.0s
 => [internal] load .dockerignore                                                                                                                                                                                                      0.2s
 => => transferring context: 74B                                                                                                                                                                                                       0.0s
failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage docker.toutdo.com/org.odoo.cloudronapp:1.0.20 could not be found

Now, all you devs can see clear as day what I did wrong, but it isn't clear to me at all what I did wrong, especially since I followed the instructions. There are always assumptions that seem to exist, assumptions that a non-dev but wanna-be-dev person like me just miss. Clearly the error docker.toutdo.com/org.odoo.cloudronapp:1.0.20 could not be found is that this can't be found... but I looked to me, from the instructions, that it would be built and then "known". So do I just leave out this step? In fact, the very first time I ran this I left off the .

me@vm:~/cloudron/cloudron-odoo$ docker build --file Dockerfile --target docker.toutdo.com/cloudron-odoo:1
"docker build" requires exactly 1 argument.
See 'docker build --help'.

Usage:  docker build [OPTIONS] PATH | URL | -

Build an image from a Dockerfile

I looked at that, then the instructions, telling myself, "look carefully, you left out something", and saw the space period. But this recent error? What the heck? I have to make this directory first? I named it wrong? Let me try without the "target". So now I'm running build without the --target, and 410s (2/3) in, it's still building.

The message at least tells me that it is looking in/pulling from => [internal] load metadata for docker.io/cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea a cloudron source. So I guess it couldn't find one with the name I used for target; but it wasn't clear to me that the name had to be of an existing image. But I also can't find any reference to a ```docker.io/coudron/base:3.2" in this cloudron-odoo repository, so, how in the world did it know to use that?

Well, this is a Help forum, not a "Teach Programming" forum, so I don't really expect anyone to spend more time trying to help me comprehend this stuff. I'll eventually get it. I hope. I just need to find a source which covers the "assumptions". Thanks again.

[timconsidine]

@scooke hope this is not a thick question but exactly which odoo repository are you cloning and building from ? Do you have a link?
I might give it a try.

How it knows which base to use ? It is stated in the Dockerfile on the line FROM .....

Keep persevering. I don't think people mind a blurred line between Help and Tutorial when the questions are good ones (as here).

[BrutalBirdie]

@timconsidine yea the source would be really helpful for debugging.

[BrutalBirdie]

@timconsidine I think it might be this: https://github.com/njsubedi/cloudron-odoo

https://forum.cloudron.io/topic/1256/odoo-distributed-business-apps/25?_=1648412597488

[BrutalBirdie]

git clone git@github.com:njsubedi/cloudron-odoo.git

cd cloudron-odoo

docker build --file Dockerfile --target dr.cloudron.dev/com.odoo.cloudronapp:0.0.1 .

docker push dr.cloudron.dev/com.odoo.cloudronapp:0.0.1

cloudron install -l odoo.cloudron.dev --image dr.cloudron.dev/com.odoo.cloudronapp:0.0.1

App is being installed.                                                                                                                                                                                                                          => Queued                                                                                                              
=> Registering subdomains 
=> Registering location: odoo.cloudron.dev ....... 
=> Setting up addons
=> Waiting for DNS propagation ...
=> Wait for health check ...........                                                                                                                                                                                                           App is installed.

and: https://odoo.cloudron.dev

login is admin:admin all working for me.

[scooke]

@timconsidine This is from @nj's github, https://github.com/njsubedi/cloudron-odoo

[scooke]

@BrutalBirdie Interesting... I'm at 3100+ seconds of build time, and it's still going.
Is that normal? I ran it without the --target option.

[BrutalBirdie]

@scooke No that is nor normal.
Maybe you can try my steps with copy and paste.

[timconsidine]

@scooke errrr I think the --target or -t option is MANDATORY
You need to tell docker what repo "to build the project into".

I just cloned the repo and built without a hitch.

[scooke]

me@VM:~/cloudron/cloudron-odoo$ docker build --file Dockerfile --target docker.toutdo.com/com.odoo.cloudronapp:0.0.1 .
[+] Building 0.3s (2/2) FINISHED
 => [internal] load build definition from Dockerfile                                                                                                                                                                                             0.1s
 => => transferring dockerfile: 38B                                                                                                                                                                                                              0.0s
 => [internal] load .dockerignore                                                                                                                                                                                                                0.1s
 => => transferring context: 34B                                                                                                                                                                                                                 0.0s
failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage docker.toutdo.com/com.odoo.cloudronapp:0.0.1 could not be found

I'm using my Docker Registery which I've installed at docker.toutdo.com, as you can see, but it's that same error about not finding it. I need to use dr.cloudron.dev (which I've been assuming can be changed)?

[timconsidine]

@scooke so MY terminal output for what you have above is :

TC-MBP-13:cloudron-odoo timconsidine$ docker build -t tcmbp132021/cloudron-odoo:a .
[+] Building 139.3s (11/17)                                                                                                                 [+] Building 139.5s (11/17)                                                                                                                 
 => [internal] load build definition from Dockerfile                                                                                   0.1ss
 => => transferring dockerfile: 1.95kB                                                                                                 0.1ss
 => [internal] load .dockerignore                                                                                                      0.1ss
 => => transferring context: 74B                                                                                                       0.0ss
 => [internal] load metadata for docker.io/cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263  33.5ss

I notice your output reports smaller file sizes
My first suspicion would be a network error.
Maybe compounded by you doing this in a local VM ?
I don't know, just taking wild stabs in the dark.
I don't think it is a process issues (commands), smells like network or environment issue to me.

[scooke]

@timconsidine Could be. It's late where I am, so I'm hitting the hay. Thanks again, I'll take another stab in the morning!

[timconsidine]

@scooke

I'm using my Docker Registery which I've installed at docker.toutdo.com, as you can see, but it's that same error about not finding it. I need to use dr.cloudron.dev (which I've been assuming can be changed)?

Yes, not just 'can', generally you should change it, because the image which is built goes into your repo that you have logged into.

[timconsidine]

@scooke good sleep !
always helps.
You will get this nailed, don't worry.

[timconsidine]

@scooke the following from your message looks strange to me :

[+] Building 0.3s (2/2) FINISHED
 => [internal] load build definition from Dockerfile                                                                                                                                                                                             0.1s
 => => transferring dockerfile: 38B  

If I read that correctly, your build process only received a Dockerfile of 38Bytes.
My Dockerfile in the folder of the cloned repo is 1.9KB - NB kilobytes.
38B is hardly enough to specify the base image correctly, let alone the rest of the build instructions.

Maybe do a directory listing and compare to the github listing ?
I withdraw my wild stab 'network' or 'environment' guess.
Instead I make a wild stab 'corrupt github clone' or 'corrupt github download / extraction'.

[timconsidine]

@scooke another thought .....
I went back to your very first message in this topic, and noticed this.

I'm also logged into my Cloudron using the cli on the Ubuntu VM

I might be reading this wrongly.
But I am NEVER logged in to my Cloudron server when I am building apps for deployment.
Raises the thought in my head : are you building the Odoo app actually on the Cloudron server ??!!
it should be built on local machine, then pushed to docker registry.
Then cloudron install etc should be run locally which does the connection to the Cloudron server.
No need to be on the Cloudron server at all while building.

I am still thinking the issue is mostly a corrupt clone from github.
But worth being clear where the build process is being run.

Anyway, off to bed also.