Thanks for jumping on this right away :) I'm having troubles getting it to work. I'm in a dir called "allura-othername" and using this commit. I do NOT have COMPOSE_PROJECT_NAME=allura set. It works fine through most of the docker setup commands on a fresh VM, but then at this point it errors out. Not sure what I'm doing wrong.
$ docker-compose run taskd paster setup-app docker-dev.ini
Pulling outmail (allura_web:latest)...
Pulling repository docker.io/library/allura_web
ERROR: Error: image library/allura_web:latest not found
Also we'll need to put the Apache License header in this file, or add it to rat-excludes.txt if it's not possible to put a comment in the file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
**history**
2939 docker-compose build
2940 docker-compose run web scripts/init-docker-dev.sh
2941 docker-compose run taskd paster setup-app docker-dev.ini
2942 docker-compose restart solr
2944 docker-compose up -d
Although, while reading this I remembered about a bookmark that I have that might help. Maybe it is happening due to some stale image or the build failing in the previous docker-compose build step causing it to go look online on docker.io. https://coderwall.com/p/ewk0mq/stop-remove-all-docker-containers has a two liner through which you can delete all docker images on the machine and then try docker-compose build again
Also we'll need to put the Apache License header in this file, or add it to rat-excludes.txt if it's not possible to put a comment in the file.
dotenv files support # for comments. I'll add that and refresh the MR.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had set COMPOSE_PROJECT_NAME= in my shell environment, thinking that blanking it out would remove it. But I was wrong, that actually set the env var but to an empty value, and prevented the .env file var from being used. After I properly removed the env var from my shell, now everything works fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for jumping on this right away :) I'm having troubles getting it to work. I'm in a dir called "allura-othername" and using this commit. I do NOT have
COMPOSE_PROJECT_NAME=allura
set. It works fine through most of the docker setup commands on a fresh VM, but then at this point it errors out. Not sure what I'm doing wrong.Also we'll need to put the Apache License header in this file, or add it to
rat-excludes.txt
if it's not possible to put a comment in the file.I did not face this problem while trying it in the release version folder allura-1.5.0
I followed https://forge-allura.apache.org/docs/getting_started/installation.html#using-docker
Although, while reading this I remembered about a bookmark that I have that might help. Maybe it is happening due to some stale image or the build failing in the previous
docker-compose build
step causing it to go look online on docker.io. https://coderwall.com/p/ewk0mq/stop-remove-all-docker-containers has a two liner through which you can delete all docker images on the machine and then trydocker-compose build
againdotenv files support
#
for comments. I'll add that and refresh the MR.Yea I tried twice on a completely fresh host (using docker-machine and new linux VMs within virtualbox).
I just upgraded to
docker-compose version 1.8.0, build f3628c7
so my environment should support that.env
file......I think the difference here is the allura_web:latest
:latest
is being added. I'll search on this and let you know.I had set
COMPOSE_PROJECT_NAME=
in my shell environment, thinking that blanking it out would remove it. But I was wrong, that actually set the env var but to an empty value, and prevented the.env
file var from being used. After I properly removed the env var from my shell, now everything works fine.