nomad.yaml is not needed? I think because of that, settings in nomad.yaml are not taken into the docker container. What should I do? @laurih or anyone knows about this change?
The README says: “If you want to use the nomad.yaml from this repository you also need to comment out the inclusion of the nomad.yaml under the volumes key of those services in the docker-compose.yaml”
I think it is commented out by default in order to not interfere with an existing config file that you may have in an existing image, but in a fresh install you probably always want to uncommment it. @hampusnasstrom: I think you know more about this? If this default is confusing for people, we could think about uncommenting it by default, and then advising people to comment it out for an existing installation.
@sherin the line is commented out because the nomad.yaml from the remote repository is included in the docker image. If you instead want to use the local nomad.yaml file on your server you should uncomment those lines in the docker-compose.yaml.
@laurih we want to keep it commented out as default since most Oases are administrated by someone at IT who does not know/care how to configure the nomad.yaml. In this way the application admin can instead configure the Oasis by changing the nomad.yaml on the remote repository and all the sys admin needs to do is docker compose down/pull/up.
Ok, this makes perfect sense, thanks for the clarification @hampusnasstrom !
So @sherin you should have a copy of configs/nomad.yaml in your Docker image already if you follow the template. That file should be up to date if you have built the image with the most recent state of the repository, and in a typical scenario there should not be need to uncomment this mounting of the file.
If you still encounter problems with not getting your configuration loaded into your Oasis, let us know. One way to debug is this e.g. to load the Docker image you have built and take a look at the nomad.yaml files that is inside there.