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 up fails, manifest unknown #53

Closed
dav-ell opened this issue Nov 5, 2019 · 5 comments
Closed

docker-compose up fails, manifest unknown #53

dav-ell opened this issue Nov 5, 2019 · 5 comments

Comments

@dav-ell
Copy link

dav-ell commented Nov 5, 2019

$ docker-compose up
ERROR: manifest for bde2020/hadoop-namenode:2.0.0-hadoop3.1.3-java8 not found: manifest unknown: manifest unknown

Can be fixed by changing 2.0.0-hadoop3.1.3-java8 to latest in docker-compose.yml. Looks like there's no tag in docker hub for 2.0.0-hadoop3.1.3-java8.

@gmouchakis
Copy link
Contributor

@dav-ell thanks for pointing this out. This will be fixed soon.

@gmouchakis
Copy link
Contributor

fixed.

@GuillaumeDesforges
Copy link

GuillaumeDesforges commented Feb 4, 2020

I got the error

Pulling namenode (bde2020/hadoop-namenode:2.0.0-hadoop3.2.1-java8)...
ERROR: manifest for bde2020/hadoop-namenode:2.0.0-hadoop3.2.1-java8 not found: manifest unknown: manifest unknown

fixed changing to bde2020/hadoop-namenode:latest for this one and others

@gmouchakis
Copy link
Contributor

Hi @GuillaumeDesforges. Probably the images were still building when you tried to pull. They are ready now.

@GuillaumeDesforges
Copy link

Thanks for the follow up. My humble recommendation would be to make the changes in a PR, and lock the merge until the Docker images are available on the Hub, as it would prevent such "false alarms" (unlikely to happen, but it happened nevertheless for me).

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

3 participants