# Sidekiq fails to start after Zeitwerk on docker dev

**URL:** <https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031>\
**Category:** Development\
**Created:** [October 2, 2019, 10:44am UTC](https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031 "2019-10-02T10:44:03Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![kris.kotlarek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kris.kotlarek/32/176919_2.png) [@kris.kotlarek](https://meta.discourse.org/u/kris.kotlarek)\
**Post date:** [October 2, 2019, 11:32pm UTC](https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031/13 "2019-10-02T23:32:35Z")

</div>

Ok, I know what happened here, it is my fault. I removed a lot of `require_dependency` since they are not required anymore when using Zeitwerk autoloader.

However, in `application.rb` we got that:

```plaintext
if !Sidekiq.server?
  config.autoload_paths += Dir["#{config.root}/lib"]
end

```

Which means that Sidekiq is not looking for `lib` directory to find dependencies and we explicitly define what is required in specific files.

I can bring back that `require_depenedency` for files which are used by Sidekiq or remove that guard in `application.rb`.

I guess that we used that explicit `require` to save some memory for workers, so probably we should follow that path. I will bring back `require_dependency`

@sam what is your opinion?

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-fails-to-start-after-zeitwerk-on-docker-dev/130031)._