You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for such interesting integration
I'm not so familiar with Ruby, could you please explain in a few words sense of this change?
When I run from default docker-compose file seems like bridge container stop working, I have following error
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "bin/boot": stat bin/boot: no such file or directory: unknown
But when I switch back from CMD ["bin/boot"] to CMD bundle exec puma -C config/puma.rb everything is ok
The text was updated successfully, but these errors were encountered:
Hello Douglas,
First of all, thank you for such interesting integration
I'm not so familiar with Ruby, could you please explain in a few words sense of this change?
When I run from default docker-compose file seems like bridge container stop working, I have following error
But when I switch back from
CMD ["bin/boot"]
toCMD bundle exec puma -C config/puma.rb
everything is okThe text was updated successfully, but these errors were encountered: