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

Getting 404 - Undefined #490

Open
Bottleface opened this issue Nov 15, 2024 · 0 comments
Open

Getting 404 - Undefined #490

Bottleface opened this issue Nov 15, 2024 · 0 comments

Comments

@Bottleface
Copy link

Ran into an error with a new docker image that I am using. WUD seems to fail when doing something with this container. I've got DEBUG logs on, and though I'm getting a stack trace it's not really helpful at telling me exactly what is wrong, only that it has a problem with this specific container.

The image/container in question is hosted on ghrc.io. I am able to see the hash of the image with the latest tag in the WUD INFO logs, so it seems that WUD is able to pull and see the manifest. The repository doesn't appear to be deprecated and seems to be normal as far as I can tell. It's a public repository, I am able to process other images on ghrc.io without issue, so I think I have the registry configured correctly in my docker-compose file.

Here are the logs and stack trace in question.

WARN whats-up-docker/watcher.docker.local: Error when processing some containers (Cannot read properties of undefined (reading 'tag')) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at /home/node/app/node_modules/request-promise-native/node_modules/request-promise-core/lib/plumbing.js:97:41 at new StatusCodeError (/home/node/app/node_modules/request-promise-native/node_modules/request-promise-core/lib/errors.js:32:15) StatusCodeError: 404 - undefined

DEBUG whats-up-docker/watcher.docker.local: 404 - undefined (container=local_rollerblades)

WARN whats-up-docker/watcher.docker.local: Error when processing (404 - undefined) (container=local_rollerblades)

Is there anything else I can do to get a better error log so I can see what specifically it's complaining about?

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

1 participant