# Docker dev only starting critical sidekiq queue
**URL:** https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242
**Category:** Bug
**Created:** [March 2, 2017, 5:12pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242 "2017-03-02T17:12:00Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [March 2, 2017, 5:12pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/1 "2017-03-02T17:12:01Z")
Currently when using `d/sidekiq` to run sidekiq in the docker dev image, it starts a sidekiq process only for the critical queue.
The problem line is:
[https://github.com/discourse/discourse/blob/master/bin/docker/sidekiq#L4](https://github.com/discourse/discourse/blob/master/bin/docker/sidekiq#L4)
When I change `sidekiq -q critical,low,default` to `sidekiq -q default,critical,low` it starts a process only for the default queue, so there’s something wrong with the commas.
The workaround I’m using is just removing ` -q critical,low,default` in its entirety, which starts a process servicing every queue.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 2, 2017, 5:34pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/2 "2017-03-02T17:34:38Z")
Sure, send a pr through to fix
---
### Author:  [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [March 2, 2017, 5:43pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/3 "2017-03-02T17:43:46Z")
[https://github.com/discourse/discourse/pull/4735](https://github.com/discourse/discourse/pull/4735)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 2, 2017, 5:54pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/4 "2017-03-02T17:54:05Z")
> [@LeoMcA](#):
>
> The workaround I’m using is just removing -q critical,low,default in its entirety, which starts a process servicing every queue.
are you 100% sure of that, I am finding this super confusing
---
### Author:  [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [March 2, 2017, 6:01pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/5 "2017-03-02T18:01:14Z")
Yep, but from playing around I’ve also found `-q critical -q low -q default` works, which is a clearer fix, so I’ve updated my PR.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [March 2, 2017, 6:32pm UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/6 "2017-03-02T18:32:50Z")
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [March 5, 2017, 3:22am UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/7 "2017-03-05T03:22:24Z")
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [March 5, 2017, 3:22am UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/8 "2017-03-05T03:22:26Z")
I believe we don’t need to pass the queue options in dev since we have
>
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 11, 2018, 12:40am UTC](https://meta.discourse.org/t/docker-dev-only-starting-critical-sidekiq-queue/58242/9 "2018-01-11T00:40:16Z")