Skip to content
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 Kafka container restarting on Mac intel processor #29022

Closed
avgupta456 opened this issue Oct 1, 2021 · 7 comments · Fixed by #28672
Closed

Docker Kafka container restarting on Mac intel processor #29022

avgupta456 opened this issue Oct 1, 2021 · 7 comments · Fixed by #28672
Assignees

Comments

@avgupta456
Copy link

Environment

self-hosted (onpremise deployment)

Version

21.10.0.dev0

Steps to Reproduce

  1. Clone from GitHub master branch
  2. Follow instructions at https://develop.sentry.dev/environment/ to setup environment
  3. sentry upgrade, sentry devservices up sentry devserver --workers
  4. Observe Docker containers, specifically sentry_kafka

Using MacBook Pro 2020 w/ Intel Core, Docker v20.10.8

Expected Result

Containers are all running and user is able to navigate to localhost:8000 and view new errors for current projects.

Actual Result

The Kafka container is repeatedly restarting. When I trigger an event for a project, I do not see any events on the issues dashboard.

Screen Shot 2021-10-01 at 5 21 05 PM

@armenzg armenzg self-assigned this Oct 1, 2021
@armenzg
Copy link
Member

armenzg commented Oct 4, 2021

Hi @avgupta456 I've noticed that your version says 5.1.2, however, we're now using 6.2.0; would you mind stopping the containers, deleting the old container and try again?

@getsentry-release
Copy link

Routing to @getsentry/open-source for triage. ⏲️

@avgupta456
Copy link
Author

@armenzg sorry I think I was testing reverting the version update in case that fixed anything. Attached is a screenshot showing the same problem with version 6.2.0

Screen Shot 2021-10-04 at 12 58 37 PM

@BYK
Copy link
Member

BYK commented Oct 4, 2021

I mean the error seems pretty clear: the data volume is not writable?

Also, if you can share text logs instead of screenshots, it would be a lot easier for us to dig through them.

@avgupta456
Copy link
Author

Here are the text logs

===> User

uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)

===> Configuring ...

===> Running preflight checks ... 

===> Check if /var/lib/kafka/data is writable ...

===> User

uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)

===> Configuring ...

===> Running preflight checks ... 

===> Check if /var/lib/kafka/data is writable ...

===> User

uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)

===> Configuring ...

===> Running preflight checks ... 

===> Check if /var/lib/kafka/data is writable ...

===> User

uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)

===> Configuring ...

Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !

Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !

Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !

@armenzg
Copy link
Member

armenzg commented Oct 4, 2021

@BYK We already landed a fix that worked on Apple M1 yet it does not seem to work on Intel. On an initial investigation, I noticed that I can start the image with the commands listed here yet sentry devservices up kafka fails to do it properly.

I'm leaning towards backing my code out and investigate later. Dealing with the ClickHouse image not working is currently the big fish to fry.

@armenzg
Copy link
Member

armenzg commented Oct 4, 2021

Related #28672

armenzg added a commit that referenced this issue Oct 4, 2021
…28574)" (#28672)

This reverts commit b4bfb00.

Originally (see [originally reported issue](#28574 (comment))), instead of reverting my change, I landed a fix that only seems to work on Apple M1 (see fix #28724). Nevertheless, It seems that the *Intel* images would still fail with the same error (see issue #29022) with:
> Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !

Let's revert it and I will try again later.

Fixes #29022
@github-actions github-actions bot locked and limited conversation to collaborators Oct 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants