custom-project Docker error

[Krasnomakov]

custom-project docker container is not composing

missing files

potentially missing whole openremote folder

Or some paths are wrong...

docker compose -fprofile/dev-testing.yml up --build -d
open ../custom-project/openremote/profile/deploy.yml: no such file or directory

---

Also in command from the manual \ instead of "/" in the command.

[Krasnomakov]

Seems like custom-project has docker files from default "openremote" repo. And inherited paths from it.

Trying to fix it now.

[Krasnomakov]

If renaming "custom-project" directory to "openremote" it looks for /openremote/openremote/profile/deploy

Thus, paths in docker files are from initial repo and don't work with custom-project

And something else is wrong, since it tries to seek for openremote subfolder...

[Krasnomakov]

Inside /profile/dev-testing.yml removed "../openremote/" part

Then it correctly navigates to profile folder

However, there is no deploy.yml file in it. Compilation doesn't go through

_--

I see now that in default "openremote" repo profile directory has deploy.yml

...

To sum it up, there are path errors and missing files in custom-project if trying to build it according to the manual.

[Krasnomakov]

After cloning default openremote repo and manually copying the /profile/deploy.yml file into custom project, renaming "custom-project" directory into "openremote" and removing "../openremote/" part from dev-testing.yml from three lines (13, 32 and 35) it compiled.

[pankalog]

Hey @Krasnomakov ,

Thanks for the issue! It seems like we overlooked that part when performing the migration of the custom project template to our release management system, since there used to be the openremote submodule that pointed to the main openremote Git repository.

I'll figure out the best course of action for this and try to update this repo so that the profiles work.

Thanks for the heads-up!

[MartinaeyNL]

This is a known issue for most of the contributors here @pankalog @Krasnomakov.
It indeed was a annoying side-effect of migrating away from Git submodules.

There's been some thinking on how to resolve this.
We'd preferably keep inheriting the deploy.yml file from the main repository, instead of the headache to maintain two files.
@pankalog, Rich and Wouter already spent some time thinking about this, so you can check with them.

[ebariaux]

This is covered by Custom project: docker-compose files reference submodule that is not present anymore · Issue #1620 · openremote/openremote