How do I do this??

[scooke]

I've resumed attempts, and keep failing on both my Ubuntu VM and Windows Terminal/Powershell:

=> => transferring context: 74B                                                                                                                                                                             
failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage dr.cloudron.dev/com.odoo.cloudronapp:0.0.1 could not be found

This seems like a network problem, but in my Docker I have what I think are all the correct options for integrating Windows Docker with WSL2 Ubuntu.

EDIT: In the last 30 minutes I have:
changed DNS setting in Docker Desktop (and back)
Changed "buildkit" from true to false (in Docker Desktop)
Deleted config.json in my Ubuntu ~/.docker directory
Cleaned and Purged in Desktop
Restarted Docker Desktop

And after each of those, if my Ubuntu WSL was running, I'd restart.

I still keep getting:

Error response from daemon: failed to reach build target dr.cloudron.dev/com.odoo.cloudronapp:0.0.1 in Dockerfile

@timconsidine No, I'm not logged into my Cloudron box, this is all local.

Anyways, time for work, I'll come back later.

[timconsidine]

@scooke I did internet search for
failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage
This produced interesting comment on https://stackoverflow.com/questions/64221861/an-error-failed-to-solve-with-frontend-dockerfile-v0

I had the same issue and all I had to do was to capitalize the Docker configuration filename:
dockerfile > didn't work
Dockerfile > did work

I see in your example earlier you are using the capitalised version.
But lower down in that thread it refers to "better practice" to use docker build --file ./Dockerfile -t <etc> to ensure it references folder in directory.
Personally I never use --file Dockerfile as it is default.
Also see a comment about WSL and closing terminal.
Also a comment about using DOCKER_BUILDKIT=0 docker build . to track the exact error.
Have a read of thread and see if any of it applies.

I would :

• close terminal and open it again
• cd to directory
• run docker build -t docker.toutdo.com/com.odoo.cloudronapp:0.0.1 n.b. without the --file directive
• see what happens !

[scooke]

@scooke Couldn't resist another quick effort:

This time I just followed @nj's instructions in the gihub repositroy and ran simply cloudron build. This prompted me for a docker repository, so I entered mine along with the suggested image name, com.odoo.cloudronapp, and then this was followed by a message stating: Building locally as docker.toutdo.com/com.odoo.cloudronapp:bunchofnumbersandletters and the build commenced. (Oh oh, I left out a username thinking that registry/username/com.odoo.cloudronapp meant registry OR username. Will this be a problem?)

Thus far it seems like using dr.cloudron.dev was the wrong thing for me to use... but it wasn't clear why!

Well, this also fails in the end. The error message says it can't find the manifest, App installation error: Installation failed: Unable to pull image docker.toutdo.com/com.odoo.cloudronapp. message: (HTTP code 404) unexpected - manifest for docker.toutdo.com/com.odoo.cloudronapp:latest not found: manifest unknown: manifest unknown statusCode: 404

The build asked for a docker repository, I gave it mine, it built, and then at the end was automatically pushed to my repository. I can see it in the web GUI.

I did run the install command without the tag on the image, so I am trying it again with the tag.

SUCCESS> I guess it needed the tag to install properly.

OK, I really do need to stop and get to work, just want you all to know I did seemingly successfully clone, build, push and install the Odoo app kindly prepped by @nj... thank you! And thank you to @timconsidine and @BrutalBirdie for helping me out too.

My last questions are: What do I do with the original clone and build directory? Leave it? Delete it? How will I update the image later if not by doing it all over again??

Ultimately, it seems to me that the whole point of the Registry is mostly to have a place to keep built Docker images. That's it. I guess that's helpful.

[BrutalBirdie]

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

Thus far it seems like using dr.cloudron.dev was the wrong thing for me to use... but it wasn't clear why!

Of course dr.cloudron.dev is not wrong for YOU because its MY server it was an example, you need to replace dr.cloudron.dev with your docker registry app URL.

[scooke]

@BrutalBirdie Sure, I see that now. It was one of many assumed pieces of knowledge that I come across while trying to learn this stuff. It's assumed I will realize this is your server. One thing that definitely helped me misunderstand is the cloudron.dev bit... I initially thought that, ok, this is coming from cloudron somehow. Anyway, one hurdle hurdled. One good lesson learned. One detail I will be sure to highlight when I'm helping someone out.

The second assumption was that I would know that the actual proper target would be asked of me when I ran build, but that wasn't clear at all, in many tuts I've been looking at. Good thing that the cloudron build prompt gave an example too, as otherwise, even with my own Docker Registry installed, I honestly would not have known what to put there exactly. And even then, after it was built, it wasn't clear to me that I needed to include that long alphanumeric tag either on the install command. When it didn't work, and the message didn't make sense, I figured I'd try adding that lengthy bit even though all other examples I've seen have a super short one, like yours! (:0.0.1) or the BBB one (:1.0.20)

So yes, it's installed! And running.

But about the original clone and build directory? Do I leave it, taking up space? Do I need it still?

[BrutalBirdie]

@scooke

But about the original clone and build directory? Do I leave it, taking up space? Do I need it still?

You can delete it.
Buy if @nj decides to release an update you will have to clone it again, and build the update.

@BrutalBirdie Sure, I see that now. It was one of many assumed pieces of knowledge that I come across while trying to learn this stuff. It's assumed I will realize this is your server. One thing that definitely helped me misunderstand is the cloudron.dev bit... I initially thought that, ok, this is coming from cloudron somehow. Anyway, one hurdle hurdled. One good lesson learned. One detail I will be sure to highlight when I'm helping someone out.

Hmmmm I was thinking if I should do the example with placeholders so its more clear.
Next time placeholders will be used again to highlight the user needs to replace this part themself.

The second assumption was that I would know that the actual proper target

There is no 'proper' --target its your own decision how to name the target, I go with the id from the CloudronManifest.json.

like yours! (:0.0.1) or the BBB one (:1.0.20)

Because, again its your choice how the image is tagged.

cloudron build --help
Usage: cloudron build [options]

Build an app

Options:
--build-arg <namevalue>                 Build arg passed to docker. Can be used multiple times (default:
[])
--build-service-token <token>           Build service token
-f, --file <dockerfile>                 Name of the Dockerfile
--set-repository [repository url]       Change the repository
--set-build-service [buildservice url]  Set build service app URL
--local                                 Build docker images locally
--no-cache                              Do not use cache
--no-push                               Do not push built image to registry
--raw                                   Raw output build log
--tag <docker image tag>                Docker image tag. Note that this does not include the repository
name
-h, --help                              display help for command

The --tag option lets you chose a tag instead of the cryptic hash.