zammad:master ← zammad:fix-container-env
My versions are
```
Docker version 24.0.5, build ced0996
Docker Compose versi…on v2.20.2
```
I dug deeper and noticed that the `.env` suggestion right now is tag version `66` which is fairly old (we're at `119` right now). Suddendly it works. The image version is very important and should be bumped together with this PR to reduce confusions for others just like I had.
With this the entrypoint variant with exec also works as expected:
```
root@dockertest:/opt/zammad-docker-compose# docker exec -ti zammad-docker-compose-zammad-railsserver-1 /docker-entrypoint.sh rails r "pp Setting.count"
I, [2023-08-23T18:53:15.098150 #32] INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2023-08-23T18:53:15.114664#32-5380] INFO -- : Using memcached as Rails cache store.
I, [2023-08-23T18:53:15.114785#32-5380] INFO -- : Using the Redis back end for Zammad's web socket session store.
I, [2023-08-23T18:53:16.487167#32-5380] INFO -- : Setting.set('models_searchable', ["Chat::Session", "KnowledgeBase::Answer::Translation", "Organization", "Ticket", "User"])
251
```
Sorry for the confusion on my end here.
---
> We'd have to make sure this is clearly documented. What do you think?
Definitely should be documented. It's not straight forward.
We also could implement some kind of wrapper like we have in package installations `zammad run ...`. Just as an idea for lazy people like me. That variant is still shorter than the entrypoint variant. But that's just me possibly.
---
Btw I also build a local container to test my `bash` variant by defining bash to be the shell to be in the container.
That variant however was not solving my above points so I discarded it.
