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

favicon not rendering correctly #24

Closed
trym-b opened this issue Sep 6, 2023 · 4 comments · Fixed by #25
Closed

favicon not rendering correctly #24

trym-b opened this issue Sep 6, 2023 · 4 comments · Fixed by #25

Comments

@trym-b
Copy link
Contributor

trym-b commented Sep 6, 2023

There is something wrong with the current icon, as it does not render properly, and displays the following error message when accessed directly:
image

To get the error above, go to this url where solrwayback is deployed: https://<domain/IP>/solrwayback/favicon.ico

@trym-b
Copy link
Contributor Author

trym-b commented Sep 6, 2023

When testing locally, simply modify the Dockerfile.solrwayback with the following diff

diff --git a/Dockerfile.solrwayback b/Dockerfile.solrwayback
index a54bd6f..778c4d9 100644
--- a/Dockerfile.solrwayback
+++ b/Dockerfile.solrwayback
@@ -49,3 +49,5 @@ COPY --from=solrwayback-bundle \
 
 # Set URL icon for the web application
 COPY favicon.ico ${CATALINA_HOME}/webapps/solrwayback/
+COPY solrwayback.properties /root/
+COPY solrwaybackweb.properties /root/
\ No newline at end of file

The icon did appear:
image

@maeb
Copy link
Member

maeb commented Sep 7, 2023

I suspect that git-lfs has something to do with this and that the icon in the container image is not actually an icon but just an ASCII-text file.

When you build the image locally you have got the actual icon in your path and that is why it works locally.

@trym-b
Copy link
Contributor Author

trym-b commented Sep 8, 2023

As far as I can tell we checkout the code using LFS:

https://github.com/nlnwa/solrwayback-adaption/blob/main/.github/workflows/release.yml#L27

@maeb
Copy link
Member

maeb commented Sep 8, 2023

Ok, found the issue: docker/build-push-action#312

Seems like we need to add a context: docker/build-push-action#312 (comment)

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.

2 participants