Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker-compose not working out of the box #19

Closed
luandro opened this issue Apr 4, 2019 · 4 comments
Closed

Docker-compose not working out of the box #19

luandro opened this issue Apr 4, 2019 · 4 comments

Comments

@luandro
Copy link

luandro commented Apr 4, 2019

I may be missing something. But I basically cloned this repo, changed .env and ran docker-compose up.

This is the error I get:

ERROR: for pkp_ojs  Cannot start service ojs: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/root/ojs/config/ojs.config.inc.php\\\" to rootfs \\\"/var/lib/docker/overlay2/2fb8a4479786e9ceb0bf5304a2154f9967c7f6ea5ae0888f1eadb7e67ff7e4e1/merged\\\" at \\\"/var/lib/docker/overlay2/2fb8a4479786e9ceb0bf5304a2154f9967c7f6ea5ae0888f1eadb7e67ff7e4e1/merged/var/www/html/config.inc.php\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for ojs  Cannot start service ojs: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/root/ojs/config/ojs.config.inc.php\\\" to rootfs \\\"/var/lib/docker/overlay2/2fb8a4479786e9ceb0bf5304a2154f9967c7f6ea5ae0888f1eadb7e67ff7e4e1/merged\\\" at \\\"/var/lib/docker/overlay2/2fb8a4479786e9ceb0bf5304a2154f9967c7f6ea5ae0888f1eadb7e67ff7e4e1/merged/var/www/html/config.inc.php\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

Any tips on how to get this working? Am I missing something?

Cheers!

@Potomac54
Copy link

Potomac54 commented Apr 4, 2019

Hello @luandro,

check the path of your volumes you have set in the docker-compose.yml file :

volumes:
 - /etc/localtime:/etc/localtime           
 - ./files/private:/var/www/files       
 - ./files/public:/var/www/html/public  
 - ./files/logs:/var/log/apache2   
 - ./config/ojs.config.inc.php:/var/www/html/config.inc.php  
 - ./config/apache.htaccess:/var/www/html/.htaccess        
 - ./config/php.custom.ini:/usr/local/etc/php/conf.d/custom.ini

you must have a file "./config/ojs.config.inc.php" in the directory where docker-compose.yml file is present,

syntax for volumes is

"the path on your hard-disk (could be a directory or a file)":"the path inside the docker image"

@lucasdiedrich
Copy link
Owner

@Potomac54 and @marcbria

Thinking about @luandro 's problem, i think we should make this volumes path commented by default, we should always have an working docker-compose without changing anything. What you think guys?

Thanks.

@Potomac54
Copy link

yes it's a possibility, provide a docker-compose.yml where all volumes path will be commented, something which can make ojs "plug and play" by running "docker-compose up" command

@marcbria
Copy link
Contributor

marcbria commented Apr 5, 2019

Full agree.
Docker and docker-compose should work "out of the box".

But it's ok if we add "clues" about how to improve them... for instance, adding commented lines to give persistence to your volumes as we are doing with adminer.

BTW, would be nice to "name" volumes. I will send you a PR as soon as I found time for it.
Sorry a lot for the delay. I'm overwhelmed those days with the conference. :-(

lucasdiedrich added a commit that referenced this issue Apr 9, 2019
"Out of the box" working docker-compose.
Fix #19
lucasdiedrich pushed a commit that referenced this issue Oct 4, 2020
Fix issue #19 - Default captcha font is not avaliable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants