Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

Docker image do not start #50

Open
yannschepens opened this issue Aug 13, 2020 · 5 comments
Open

Docker image do not start #50

yannschepens opened this issue Aug 13, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@yannschepens
Copy link

Hello,

I try to use the docker image : https://registry.hub.docker.com/r/hygieiadoc/sonarcodequalitycollector.

But when I run it, it fail with : "no main manifest attribute, in sonar-codequality-collector-javadoc.jar" error.

(I build myself the image using the Dockerfile.build, and it works well)

P.S.: I'm not a java developer, so spring boot is not my cup of tea.

@rvema
Copy link
Contributor

rvema commented Aug 13, 2020

thanks for raising this issue, we will get this fixed.

@rvema rvema added the bug Something isn't working label Aug 13, 2020
@samwiskow
Copy link

FYI - I am actually seeing this on nearly all of the docker images hosted on docker hub

@rvema
Copy link
Contributor

rvema commented Dec 10, 2020

@chzhanpeng Can you validate this ? Also @samwiskow did you did you follow the instructions as in docker-instructions.

@Bhaskar1312
Copy link

I have faced the same error
xxxxxxx@cloudshell:$ docker pull hygieiadoc/sonarcodequalitycollector
Using default tag: latest
latest: Pulling from hygieiadoc/sonarcodequalitycollector
e4c3d3e4f7b0: Pull complete
101c41d0463b: Pull complete
8275efcd805f: Pull complete
556bd89391a7: Pull complete
26c447bde847: Pull complete
8b4260df6f09: Pull complete
3684adf51eef: Pull complete
b77597dc8a4e: Pull complete
db8f232bb545: Pull complete
Digest: sha256:3f0ced4d79f41b56235fd6133d6042f4ac53f2c4d1b6ac2b967812aa97e37f31
Status: Downloaded newer image for hygieiadoc/sonarcodequalitycollector:latest
docker.io/hygieiadoc/sonarcodequalitycollector:latest
xxxxxxx@cloudshell:
$ docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
hygieiadoc/sonarcodequalitycollector latest b68e7a8f2285 3 months ago 301MB
xxxxxxx@cloudshell:~$ docker run -e SKIP_PROPERTIES_BUILDER=true -v properties_location:/hygieia/config b68e7a8f2285
Skipping properties builder
cat: /hygieia/config/application.properties: No such file or directory
no main manifest attribute, in sonar-codequality-collector-javadoc.jar

@samwiskow
Copy link

@rvema - I followed the instructions, but as they are incredibly generalized and quite sparse, I'm not sure if they are actually doing what I intend to do. Is there a more complete set of instructions/options/arguments that need to be passed in for each of the containers to be started correctly?

For example, I'm running something like this command for the api container:

 docker run -d -t -p 8080:8080 --name api --link=hy-mongo:mongo -v $SOME_WINDOWS_PATH\props\api.properties:/hygieia/config/application.properties -e "SPRING_DATA_MONGODB_HOST=127.0.0.1" -e "SPRING_DATA_MONGODB_PORT=27017" -e SKIP_PROPERTIES_BUILDER=true hygieiadoc/api:v3.1.3

The container exits straight away with the logs:

SPRING_DATA_MONGODB_HOST: 127.0.0.1
SPRING_DATA_MONGODB_PORT: 27017
no main manifest attribute, in api-javadoc.jar

But it's not really clear what arguments the container is expecting, or what is going wrong. I am having similar issues with all the containers I try

OS: Windows
Docker platform: Hyper-V

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants