-
Notifications
You must be signed in to change notification settings - Fork 45
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 Trigger Fails on Some Containers #581
Comments
@jrbarronumd Do you mind sharing Docker-Compose file with containers that fail for you? |
Gladly. It a massive file, so I'll share a couple containers that worked for updating, and a couple that did not. Audiobookshelf and unifi worked, and dbbackups and LLDAP did not. Thanks!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently started using the Docker Compose trigger, in manual mode. For certain containers, it works perfectly - compose file is updated, and the container is updated. For the rest, nothing happens, and the log produces a single line, shown below. I can't seem to figure out any similarities between the failures, or the successes. Mostly all from the GHCR. It seems consistent though. When I recreate a successfully updated container at an older version, and recreate the WUD container (or not), it works to update that container every time. But it has never failed on one, and succeeded in a later attempt.
WARN whats-up-docker/container: Error when running trigger (type=dockercompose, name=local) (Cannot read properties of undefined (reading 'includes'))
WUD environment variables below:
Love this project, thank you for sharing your work!!
The text was updated successfully, but these errors were encountered: