#service "immich-microservices" has neither an image nor a build context specified: invalid compose p

1 messages · Page 1 of 1 (latest)

true fiber
#

Hello, I updated from 105.1 to 106.3. I'm using Unraid docker compose and this is how I update it.

  1. docker compose -f /boot/config/plugins/compose.manager/projects/Immich/docker-compose.yml up down
  2. Update the compose file base on the instructions.
  3. docker compose -f /boot/config/plugins/compose.manager/projects/Immich/docker-compose.yml pull
  4. docker compose -f /boot/config/plugins/compose.manager/projects/Immich/docker-compose.yml up -d --remove-orphans

The update is ok and I can access the app but the log says:

"service "immich-microservices" has neither an image nor a build context specified: invalid compose project"

What should I do?

rigid havenBOT
#

:wave: Hey @true fiber,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :blue_square: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

sullen coral
#

read the releasenotes...

#

immich-microservices was removed and integrated

true fiber
#

@sullen coral yeah that was what I did. Is it normal to have that log in the unraid?

sullen coral
#

no, thats not normal

#

did you pull the newest images

rigid havenBOT
sullen coral
#

I think the logs got cut off

true fiber
sullen coral
#

can you upload a file? I think discord cuts it off after 4000 characters

true fiber
#

Actually, there's no problem with the individual container. The problem is with the unraid immich stack logs

image.png
sullen coral
#

oh

true fiber
#

Hi, would like to follow up on how can I fix my problem, please? Thank you.

lapis glacier
#

This isn't really an Immich related issue. Somewhere in unraid, there exists a reference to the immich-microservices that you tried to remove

#

you will need to look around of how to delete that contianer / reference

true fiber
#

Finally, I found it. Thanks for giving me a hint. It was in the docker-compose.override.yml file. I don't know why but I don't create it. I think its Unraid thing. This was the content of it and I removed the microservices line.

services:
immich-server:
labels:
net.unraid.docker.managed: 'composeman'
net.unraid.docker.icon: ''
net.unraid.docker.webui: ''
net.unraid.docker.shell: ''
immich-microservices:
labels:
net.unraid.docker.managed: 'composeman'
net.unraid.docker.icon: ''
net.unraid.docker.webui: ''
net.unraid.docker.shell: ''
immich-machine-learning:
labels:
net.unraid.docker.managed: 'composeman'
net.unraid.docker.icon: ''
net.unraid.docker.webui: ''
net.unraid.docker.shell: ''
redis:
labels:
net.unraid.docker.managed: 'composeman'
net.unraid.docker.icon: ''
net.unraid.docker.webui: ''
net.unraid.docker.shell: ''
database:
labels:
net.unraid.docker.managed: 'composeman'
net.unraid.docker.icon: ''
net.unraid.docker.webui: ''
net.unraid.docker.shell: ''