Skip to content

Instantly share code, notes, and snippets.

@Yardboy
Created April 24, 2020 21:45
Show Gist options
  • Save Yardboy/a14746c822d97b38846906acde28e1cf to your computer and use it in GitHub Desktop.
Save Yardboy/a14746c822d97b38846906acde28e1cf to your computer and use it in GitHub Desktop.
New error on procfile
remote: +++ [[ ! -f /home/dokku/shards/DOKKU_PROCFILE ]]
remote: +++ procfile-util show --procfile /home/dokku/shards/DOKKU_PROCFILE --process-type web --default-port 3000
remote: ++ DOKKU_PROCFILE_START_CMD='puma -C config/puma.rb'
remote: ++ START_CMD='puma -C config/puma.rb'
remote: ++ echo 'puma -C config/puma.rb'
remote: + START_CMD='puma -C config/puma.rb'
remote: + [[ false == \f\a\l\s\e ]]
remote: ++ docker run --label=dokku -d -e PORT=3000 --env=DATABASE_URL=mysql2://mysql:54de2f4cf18ab5fd@dokku-mysql-shardsdb:3306/shardsdb --env=DOKKU_APP_TYPE=dockerfile --env=DOKKU_DOCKERFILE_PORTS=3000 --env=DOKKU_PROXY_PORT=80 --env=DOKKU_PROXY_PORT_MAP=http:3000:3000 --env=GIT_REV=9bf44d8ebd18fdc88ff391156a148cf6c23abce4 --env=RACK_ENV=production --env=RAILS_ENV=production --env=RAILS_SERVE_STATIC_FILES=true --env=REDIS_URL=redis://shardsrd:80738cf6c4eb5851551ed3f76ce287aa3821b15f490287f5e544841452e2acee@dokku-redis-shardsrd:6379 --env=SECRET_KEY_BASE=0448b7a2219f8630d06e76c969ac50542b92c84762dd966f91293145cb52bb599e564e372d2a060db618d1ac00ac41f4fb518575c37d0a8dca5c318c031b5be2 --link dokku.mysql.shardsdb:dokku-mysql-shardsdb --link dokku.redis.shardsrd:dokku-redis-shardsrd --restart=on-failure:10 -e DYNO=web.1 -e TRACE=true dokku/shards:latest puma -C config/puma.rb
remote: docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"puma\": executable file not found in $PATH": unknown.
remote: + cid=c9a134b5b981448b89e81a86d4de969863dcb044f83514015a501263fc7b038c
@Gubio
Copy link

Gubio commented Sep 23, 2020

Did you solve this error?

@Yardboy
Copy link
Author

Yardboy commented Sep 24, 2020

I know that I do not have this problem now, but without knowing what I was fighting with, I can't remember what the solution was. Did you follow a link here? If I can see where I linked it I can probably remember.

@Yardboy
Copy link
Author

Yardboy commented Sep 24, 2020

This is a dokku deploy log from an old project. The only thing that comes to mind immediately is: because I work in Windows, at one point my binstubs in the repo were not executable, so when they got to the server they wouldn't run.

I added the following to my dockerfile to make sure that doesn't happen in the future.

# make sure that binstubs are executable
RUN chmod u+x bin/*

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment