remote: Error response from daemon: Error processing tar file(exit status 1): write /app/.heroku/node/bin/node: no space left on device
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, node.js, shell
- Domain
- cloud, devops, infrastructure
Research direction
Start with bin/deploy.sh and the deployment trace in this report, then inspect the Docker/Dokku deployment step where the tar write fails at /app/.heroku/node/bin/node. Reproduce the CircleCI auto-deploy if possible and determine the deployment condition that must change; done means the documented deployment completes without the daemon's disk-space error.
Written by the indexing model from the issue text.
Description
When attempting to auto-deploy from CircleCI we are seeing the following error:
remote: Error response from daemon: Error processing tar file(exit status 1): write /app/.heroku/node/bin/node: no space left on device
Full Stack Trace:
#!/bin/bash -eo pipefail
sh bin/deploy.sh
CWD /root/repo/bin
BRANCH => close-modal
DOKKU_APP => ci
DOKKU_APP => ci-close-modal
URL => 138.68.163.126:ci-close-modal
CREATE => dokku apps:create ci-close-modal
Warning: Permanently added '138.68.163.126' (ECDSA) to the list of known hosts.
Name is already taken
WARNING: env2 was required to load an .env file: /root/repo/.env NOT FOUND! Please see: http://git.io/vG3UZ
ENV => NODE_VERSION=8.11.3 HOSTNAME=a406bd28a9d6 CI_PULL_REQUESTS=https://github.com/charterindex/application/pull/320 SERVER_IP_ADDRESS=138.68.163.126 ENVIRONMENT-VARIABLES-REDACTED!
-----> Setting config vars
YARN_VERSION: 1.6.0
PORT: 5000
JWT_SECRET: thisissecret
HOSTNAME: a406bd28a9d6
SERVER_IP_ADDRESS: 138.68.163.126
DOKKU_APP: ci-close-modal
CI: true
NODE_VERSION: 8.11.3
CI_PULL_REQUESTS: https://github.com/charterindex/application/pull/320
BASH_ENV: /tmp/.bash_env-5b3bfdabb05ef50013c42a5b-0-build
TRAVIS: false
CIRCLECI: true
-----> Restarting app ci-close-modal
! App ci-close-modal has not been deployed
REMOTE => dokku dokku@138.68.163.126:ci-close-modal
fatal: No such remote 'dokku'
dokku dokku@138.68.163.126:ci-close-modal (fetch)
dokku dokku@138.68.163.126:ci-close-modal (push)
origin git@github.com:charterindex/application.git (fetch)
origin git@github.com:charterindex/application.git (push)
KILL_NGINX => pkill nginx
SYSTEMCTL_START_NGINX => systemctl start nginx
COMMIT_HASH => bedba5b4f404b4f94b7c69eb211eaf9844ba7f28
PUSH => git push dokku bedba5b4f404b4f94b7c69eb211eaf9844ba7f28:refs/heads/master
Counting objects: 3711, done.
Delta compression using up to 32 threads.
Compressing objects: 100% (1213/1213), done.
Writing objects: 26% (965/3711)
Writing objects: 100% (3711/3711), 6.78 MiB | 5.13 MiB/s, done.
Total 3711 (delta 2415), reused 3698 (delta 2408)
remote: -----> Cleaning up...
remote: -----> Building ci-close-modal from herokuish...
remote: -----> Adding BUILD_ENV to build environment...
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote: NPM_CONFIG_LOGLEVEL=error
remote: YARN_VERSION=1.6.0
remote: NODE_VERSION=8.11.3
remote: NODE_VERBOSE=false
remote: NODE_ENV=production
remote: NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote: engines.node (package.json): 8.11.2
remote: engines.npm (package.json): 5.6.0
remote:
remote: Resolving node version 8.11.2...
remote: Downloading and installing node 8.11.2...
remote: npm 5.6.0 already installed with node
remote:
remote: -----> Restoring cache
remote: Loading 2 from cacheDirectories (default):
remote: - node_modules
remote: - bower_components (not cached - skipping)
remote:
remote: -----> Building dependencies
remote: Installing node modules (package.json)
remote:
remote: > application@1.0.0 postinstall /tmp/build
remote: > npm run elm-install && npm run elm-compile && npm run css-compile
remote:
remote:
remote: > application@1.0.0 elm-install /tmp/build
remote: > cd elm && ../node_modules/elm/binwrappers/elm-package install -y && cd ..
remote:
remote: Starting downloads...
remote:
remote: ● dwyl/elm-datepicker 2.2.0
remote: ● NoRedInk/elm-decode-pipeline 3.0.0
remote: ● elm-lang/core 5.1.1
remote: ● elm-lang/dom 1.1.1
remote: ● elm-lang/html 2.0.0
remote: ● elm-lang/http 1.0.0
remote: ● elm-lang/keyboard 1.0.1
remote: ● elm-lang/navigation 2.1.0
remote: ● elm-lang/virtual-dom 2.0.4
remote: ● justinmimbs/elm-date-extra 3.0.0
remote:
remote: Packages configured successfully!
remote:
remote: > application@1.0.0 elm-compile /tmp/build
remote: > cd elm && ../node_modules/elm/binwrappers/elm-make *.elm --output ../public/js/elm.js --yes --warn && cd ..
remote:
remote: Success! Compiled 77 modules.
remote: Successfully generated ../public/js/elm.js
remote:
remote: > application@1.0.0 css-compile /tmp/build
remote: > postcss routes/css/index.css --output public/stylesheets/style.min.css --config postcss.config.js --verbose
remote:
remote: Processing routes/css/index.css...
remote: Finished routes/css/index.css in 3.41 s
remote: up to date in 32.714s
remote:
remote: -----> Caching build
remote: Clearing previous node cache
remote: Saving 2 cacheDirectories (default):
remote: - node_modules
remote: - bower_components (nothing to cache)
remote:
remote: -----> Pruning devDependencies
remote: Skipping because npm 5.6.0 sometimes fails when running 'npm prune' due to a known issue
remote: https://github.com/npm/npm/issues/19356
remote:
remote: You can silence this warning by updating to at least npm 5.7.1 in your package.json
remote: https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version
remote:
remote: -----> Build succeeded!
remote: -----> Discovering process types
remote: Procfile declares types -> web
remote: Error response from daemon: Error processing tar file(exit status 1): write /app/.heroku/node/bin/node: no space left on device
To dokku@138.68.163.126:ci-close-modal
! [remote rejected] bedba5b4f404b4f94b7c69eb211eaf9844ba7f28 -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@138.68.163.126:ci-close-modal'
server.crt
server.key
-----> Unsetting DOKKU_PROXY_PORT
-----> Unsetting DOKKU_PROXY_SSL_PORT
-----> Setting config vars
DOKKU_PROXY_PORT_MAP: http:80:5000
-----> Setting config vars
DOKKU_PROXY_PORT_MAP: http:80:5000 https:443:5000
-----> Setting config vars
DOKKU_PROXY_PORT: 80
-----> Setting config vars
DOKKU_PROXY_SSL_PORT: 443
-----> No matching configured domains for ci-close-modal found in SSL certificate. Your app will show as insecure in a browser if accessed via SSL
-----> Please add appropriate domains via the dokku domains command
-----> Configured domains for app:
=====> A
=====> *.ademo.app
=====> 138.68.163.126
=====> ademo.app
-----> Domains found in SSL certificate:
=====> *.ademo.app
=====> ademo.app
grep: /home/dokku/ci-close-modal/VHOST: No such file or directory
-----> Configuring 138.68.163.126...(using built-in template)
-----> Configuring A...(using built-in template)
-----> Configuring *.ademo.app...(using built-in template)
-----> Configuring ademo.app...(using built-in template)
-----> App ci-close-modal has not been deployed. Skipping nginx config creation
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
- Dominant language
- Shell
- Stars
- 443
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dwyl/learn-devops
-
discuss enhancement help wanted research T25m technical
dwyl/learn-devops#112 · 1 assignee ·
-
Netcup.eu Opendiscuss help wanted research starter technical
Difficulty 5/5 Over a week Newbie friendliness 35/100
dwyl/learn-devops#111 ·
-
`Dokploy` Opendiscuss technical
Difficulty 5/5 Over a week Newbie friendliness 25/100
dwyl/learn-devops#110 ·
-
discuss T5m technical
Difficulty 5/5 Over a week Newbie friendliness 15/100
dwyl/learn-devops#109 · 1 comment ·
-
discuss enhancement help wanted priority-2 research T25m technical
Difficulty 5/5 Over a week Newbie friendliness 25/100
dwyl/learn-devops#108 · 6 comments · 1 reaction ·
All issues in dwyl/learn-devops
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·