I am deploying a Rails app, including a dedicated work to run background jobs. I want to reuse the built Rails container and just change the run time command.
I was expecting the following configuration to work:
worker:
- name: resque
image:
registry_type: DOCR
repository: <repository_name>
tag: <tag_name>
run_command: ./docker/scripts/resque.sh
envs:
- key: ENV_1
value: Value_1
...
When I trigger a deployment it fails to run the migrations with the following error:
resque | 12:23:25 starting container: starting non-root container [/cnb/lifecycle/launcher ./docker/scripts/resque.sh]: creating process: failed to load /cnb/lifecycle/launcher: no such file or directory
I have had to resort to having dedicated containers for the Rails app, Resque workers and migrations where the only difference is the runtime command
Any suggestions?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I’ve looked into this and it looks like you’ve found a bug in our new support for DOCR registries. I’ve filed a ticket internally and hope to have a fix for this soon. Thanks for reporting this. I will update this thread once the fix has been deployed.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.