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

Dockerfile fails to copy vivo home #3643

Closed
ghost opened this issue Feb 14, 2022 · 7 comments
Closed

Dockerfile fails to copy vivo home #3643

ghost opened this issue Feb 14, 2022 · 7 comments

Comments

@ghost
Copy link

ghost commented Feb 14, 2022

Describe the bug

=> ERROR [4/6] COPY ./installer/home/target/vivo /vivo-home                                                                    0.0s

To Reproduce

Follow https://github.com/vivo-project/VIVO#docker-compose

Expected behavior

Should build images and run VIVO.

Screenshots

image

Environment (please complete the following information):

  • OS: Windows
  • Browser: N/A
  • Tomcat version: N/A
  • VIVO version: master
  • Apache Solr or ElasticSearch version: N/A

Additional context

@gneissone
Copy link
Member

@wwelling Does this fix the issue? 1dd3b40

The change is already in 1.12.1-maint.

@ghost
Copy link
Author

ghost commented Feb 14, 2022

It does but will break on next version change.

@ghost
Copy link
Author

ghost commented Feb 14, 2022

Also, I checked 1.12.1-maint Dockerfile and it does not have that change but the pom does have that change.

@ghost
Copy link
Author

ghost commented Feb 14, 2022

#3644

@ghost ghost linked a pull request Feb 14, 2022 that will close this issue
@gneissone
Copy link
Member

The commit history on that PR is confusing. The relevant change is re-adding <finalName>${app-name}</finalName> to installer/home/pom.xml, the change to the Dockerfile was added then removed. That pom tag results in the target home directory being named vivo instead of vivo-installer-home-x.x.x

@ghost
Copy link
Author

ghost commented Feb 14, 2022

This works from rel-1.12.1-maint branch. Closing. Shouldn't the default branch in GitHub being the development branch? I sense some disarray still.

@ghost ghost closed this as completed Feb 14, 2022
This issue was closed.
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

Successfully merging a pull request may close this issue.

1 participant