Donal McBreen

Closing this as extra ports can be published via `options` as @sudarshan-dodiya mentioned.

Also it looks like there are some test failures - `CliAppTest#test_exec_detach` and `CommandsAppTest#test_execute_in_new_detached_container`

In Kamal 2, you can tell docker to use the `docker` driver which should pick up the local settings. The driver is limited though - you can't build multiarch images,...

Hi @Tekchanddagar. Kamal 2 will automatically create a `kamal` network and create all containers including accessories in it. Does that solve your problem here?

Closed by https://github.com/basecamp/kamal/pull/1531

Thanks @yahonda. I'm seeing the same failure with `AJ_INTEGRATION_TESTS=1 AJ_ADAPTER=sidekiq bin/test test/integration/queuing_test.rb -n test_should_interrupt_jobs`, but interestingly `bundle exec rake test:integration:sidekiq` passes ok. I'll take a look.

Looks like this is a load path issue. Sidekiq defines its [own version](https://github.com/sidekiq/sidekiq/blob/aee9da68706536fcacbaad069794644f027c3278/lib/active_job/queue_adapters/sidekiq_adapter.rb) of the adapter. If the sidekiq lib directory is before the activejob lib directory, then its adapter...

Do you have more details? The secrets for an app are stored in `~/.kamal/apps//env` and the entire `~/.kamal/apps/` directory should be removed when calling `kamal remove`.

@junket - the default path is to have `.kamal/secrets` in source control and to load the secrets from a password manager/secret store at runtime. But removing `.kamal/secrets` from source control...

Yes that is a problem, but probably not fixable without breaking existing deployments. Does something like this work as a workaround? ```yaml accessories: postgres: service: postgres- ```