Open cryptedx opened 2 months ago
Same for me with KeyError: 'docker.io/redis:6.2-alpine'
on v0.4.2
Can you please post the contents of /config/settings.yml
?
Also, try the following again:
docker compose down
./config
and ./data
contentsdocker compose up -d
I've added custom service to my stacks which is using docker.io/redis:6.2-alpine
as an image,
Unfortunately I'm not getting the KeyError
when entering Docking Station.
For sure! Here you go:
server:
cache_control_max_age: 1d
discovery_strategy: opt-out
dryrun: false
ignore_compose_stack_name_keywords:
- devcontainer
possible_homepage_labels: # order matters!
- org.label-schema.url
- org.opencontainers.image.url
- org.opencontainers.image.source
possible_image_version_labels: # order matters!
- org.label-schema.version
- org.opencontainers.image.version
python_on_whales__ignored_image_prefixes:
- docker.io/library/
- docker.io/
time_until_update_is_mature: 1w
auto_updater:
enabled: false
interval: 1d
max_concurrent: 1
I tried it. Issue persists. Sorry for the bad news.
I'm experiencing the same issue as @cryptedx . Tried the following but no change
python_on_whales__ignored_image_prefixes:
- docker.io/tensorchord/
- docker.io/library/
- docker.io/
I'm sorry guys,
but I'm not able to reproduce this issue on my side.
Here's the compose file I'm trying to reproduce with:
services:
redis-test:
image: docker.io/redis
command: ["sleep", "infinity"]
pgvecto-rs:
image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0
command: ["sleep", "infinity"]
Everything is loading just fine, no errors
If you have the know-how, try to debug it yourself and let me know if you find anything.
I have a fully working devcontainer at the root of the repository.
Just adjust the stacks location in volumes:
to the proper path for your machine.
Closing this as can't reproduce.
I have found out the issue. It is because of the sha256 checksum from immich default docker compose file at the images. When I remove it, then it is working.
redis:
container_name: immich_redis
image: docker.io/redis:6.2-alpine@sha256:d6c2911ac51b289db208767581a5d154544f2b2fe4914ea5056443f62dc6e900
healthcheck:
test: redis-cli ping || exit 1
restart: always
database:
container_name: immich_postgres
image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
can confirm, removing sha256 from immich docker-compose file fixes it. @LooLzzz could you please reopen this issue? or maybe it will be tracked in some other place with other similar KeyError problems?
Again, the thing is - I can't reproduce it on my system
services:
redis-test:
image: docker.io/redis:6.2-alpine@sha256:d6c2911ac51b289db208767581a5d154544f2b2fe4914ea5056443f62dc6e900
command: ["sleep", "infinity"]
pgvecto-rs:
image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
command: ["sleep", "infinity"]
Seems fine with no errors in the console
What am I missing here?
Could you try to setup immich? The you will have the same scenario like we have.
Could you try to setup immich? The you will have the same scenario like we have.
Yep Immich is already setup and running on my machine as well
Could you try to setup immich? The you will have the same scenario like we have. https://immich.app/docs/install/docker-compose/
Yep Immich is already setup and running on my machine as well
Is Immich setup using a single stack or did you separate the containers? Like others have posted, I too am experiencing the same bug. Removing the sha2 didn't fix the issue on my end unfortunately.
For reference, i tried this on a server that only has Immich, Docking-Station, a very few other containers. I do have docking-station working on other servers where immich is not deployed.
I have one immich docker composer stack
Hi,
I am von version 0.3.1. I tried a clean re-install.
compose-yaml
docking-station-server.log
Thanks