/bin/bash: line 1: gosu: command not found

[goganchic]

Version

22.6.0

Steps to Reproduce

1. Start Sentry with docker-compose
2. Wait for a bit
3. Check docker-compose logs

Expected Result

No errors

Actual Result

sentry-self-hosted-snuba-transactions-cleanup-1                | /bin/bash: line 1: gosu: command not found
sentry-self-hosted-snuba-cleanup-1                             | /bin/bash: line 1: gosu: command not found

[aminvakil]

$ docker exec -ti sentry-self-hosted-snuba-cleanup-1 whereis gosu
gosu: /usr/local/bin/gosu
$ docker exec -ti sentry-self-hosted-snuba-cleanup-1 gosu --help
Usage: gosu user-spec command [args]
   eg: gosu tianon bash
       gosu nobody:root bash -c 'whoami && id'
       gosu 1000:1 id

gosu version: 1.12 (go1.13.10 on linux/amd64; gc)
gosu license: GPL-3 (full text at https://github.com/tianon/gosu)

It's working fine for me, are you sure your docker has been built correctly?

[goganchic]

You run this command using shell directly, but docker-compose run this command using cron, so the command will be something like cron "0 0 * * * gosu sentry sentry cleanup --days $SENTRY_EVENT_RETENTION_DAYS". I don't think that in this case $PATH variable will be the same as for shell. But let me check this behavior one more time.

[goganchic]

The problem is not with paths: sentry-cleanup and symbolicator-cleanup have gosu, but snuba-transactions-cleanup and snuba-cleanup do not have. I think, it's because snuba-transactions-cleanup and snuba-cleanup use another base image. Does it really contains gosu?

I use such versions:

SENTRY_IMAGE=getsentry/sentry:22.6.0
SNUBA_IMAGE=getsentry/snuba:22.6.0
RELAY_IMAGE=getsentry/relay:22.6.0
SYMBOLICATOR_IMAGE=getsentry/symbolicator:0.5.1

[goganchic]

I'd checked the problem with nightly images - nothing changed: sentry-cleanup and symbolicator-cleanup have gosu, but snuba-transactions-cleanup and snuba-cleanup do not have.

If I add gosu into cron/Dockerfile - everything works as expected.

[dlouzan]

Just experiencing the same issue after updating to 22.6.0. Adding gosu to the base image as #1564 does seem to fix the problem.

/cc @max-wittig

[emmatyping]

I can reproduce this issue locally.

[emmatyping]

It looks like there was an attempt to remove gosu which may be the root cause of this: getsentry/snuba#2696, that PR has been reverted, but the revert was reverted getsentry/snuba#2777, so it looks like snuba removed gosu.