- Is polkovnik-z/docker-jobs-bundle a Laravel package?
- No. It is a Symfony bundle that registers with the Symfony kernel, DI container, console commands, and likely the event dispatcher. Laravel does not consume Symfony bundles, so you cannot just composer require it into a Laravel app. A Laravel shop would need to stand up a small Symfony sidecar service or port the orchestration logic into a Laravel-native dispatcher backed by the Docker API.
- How do I install docker-jobs-bundle in a Symfony application?
- Install it with Composer, register the bundle in config/bundles.php, and add a YAML configuration block for the Docker host and image naming. Job definitions are wired through Symfony's service container and dispatched to isolated containers. Because the last release was August 2022, verify PHP and Symfony constraints and run a spike before committing.
- Does docker-jobs-bundle work with Laravel 11?
- There is no official Laravel support. The package is built as a Symfony bundle and depends on Symfony bundle registration and DI conventions that Laravel does not use. You could host it in a separate Symfony service and call it from Laravel, but that is custom integration work rather than a Composer-only install. For Laravel-native containerized jobs, use queued workers with Horizon or a similar queue setup.
- Which PHP and Symfony versions does docker-jobs-bundle support?
- Compatibility is unproven until you verify it. The last release was August 2022, so PHP 8.2, PHP 8.3, Symfony 6.4, and Symfony 7 support should be treated as unknown. Check composer.json constraints and run a small spike on your exact target stack before relying on it.
- How does docker-jobs-bundle execute background jobs in Docker?
- It connects job definitions to Symfony's service container and runs PHP tasks in isolated Docker containers with configurable images and commands. Jobs are registered as services and dispatched using asynchronous or background execution patterns. The package assumes a reachable Docker daemon, typically through a socket mount or Docker-in-Docker. It does not manage the container runtime or host capacity for you.
- Is mounting the Docker socket safe for docker-jobs-bundle?
- Mounting /var/run/docker.sock into an application container is a well-known privilege-escalation path because socket access is effectively host-level control. Treat that as an architecture review item, not a configuration detail. Consider rootless Docker, a dedicated job runner, or a managed orchestrator such as Kubernetes Jobs or ECS. If your security model forbids Docker socket exposure, this bundle is a poor fit.
- Does docker-jobs-bundle handle retries, timeouts, and container cleanup?
- The documentation does not clearly confirm retries, timeouts, idempotency keys, or concurrency limits, so assume you may need to build them. Container cleanup, orphan removal, and log retention are operational concerns the package does not appear to own. With 19 stars and a single maintainer, expect to read the source to answer edge-case questions. Plan for your team to own these behaviors in production.
- Can I use docker-jobs-bundle with Kubernetes Jobs or AWS ECS?
- Not out of the box as far as the public material shows. The key question is whether the Docker executor is abstracted behind an interface or hard-coded to a Docker daemon. If it is hard-coded, swapping in Kubernetes Jobs or ECS would require a fork or a wrapper. If multi-runtime orchestration is a requirement, choose a native orchestrator instead.
- How do I test docker-jobs-bundle jobs in CI?
- Your CI needs a Docker daemon, either Docker-in-Docker or a mounted socket, plus image build or pull steps and a defined job-definition contract. Start with one new batch workload as a pilot and verify the exit-code and result contract back to the host. Because maintenance is thin, vendor the package into your monorepo if you need to patch it. Test cleanup, timeouts, and failure paths explicitly.
- Is docker-jobs-bundle actively maintained, and what are the alternatives?
- Maintenance is weak: the last release was August 2022, there is no release cadence in roughly three years, the repo has about 19 stars, and it has a single maintainer under the MIT license. There is little community validation of edge cases, so you will read source for answers. Alternatives include Laravel Horizon or Queue with containerized workers, Symfony Messenger with a container transport, Kubernetes Jobs and CronJobs, Dagger, Temporal, and Argo. Those have larger communities and do not bake in a Docker socket requirement.