-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpg: cannot open '/dev/tty': No such device or address #922
Comments
We have a fix in place to use |
@chorrell I think we can close this can we? |
Yes! |
longtian
added a commit
to testin/dockerfiles
that referenced
this issue
Dec 20, 2018
vsilent
pushed a commit
to trydirect/flask-formula
that referenced
this issue
Jan 11, 2019
SISheogorath
added a commit
to hedgedoc/container
that referenced
this issue
Jan 15, 2019
Seems like debian's GPG version now expects a TTY and only works without when it's explicitly definied. This patch adds the `--no-tty` option to the gpg call. `--batch` seems to include it and this way doesn't need it. This should fix the error during docker build. Additional information: nodejs/docker-node#922 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614
thewtex
added a commit
to thewtex/dockcross
that referenced
this issue
Jan 20, 2019
The base image moved from jessie to stretch, so update sources and packages. Also update gosu binary install to support gpg2 and work around: gpg: cannot open '/dev/tty': No such device or address as suggested here: nodejs/docker-node#922
thewtex
added a commit
to thewtex/dockcross
that referenced
this issue
Jan 20, 2019
The base image moved from jessie to stretch, so update sources and packages. Also update gosu binary install to support gpg2 and work around: gpg: cannot open '/dev/tty': No such device or address as suggested here: nodejs/docker-node#922 gpg: keyserver receive failed: Cannot assign requested address as suggested here: jacobalberty/unifi-docker#64
nest-don
added a commit
to inkton/docker.nest.rabbitmq
that referenced
this issue
Jan 21, 2019
petitlouis
pushed a commit
to petitlouis/basedriver
that referenced
this issue
Jan 23, 2019
…dress See issue in nodejs/docker-node#922 I backport this correction
therefromhere
added a commit
to prismaticd/docker-django-nginx
that referenced
this issue
Feb 19, 2019
thesamesam
added a commit
to thesamesam/getuto
that referenced
this issue
Aug 19, 2023
Bug: nodejs/docker-node#922 Signed-off-by: Sam James <[email protected]>
annrpom
added a commit
to annrpom/cockroach
that referenced
this issue
Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: cockroachdb#113673 Fixes: cockroachdb#113662 Fixes: cockroachdb#113659 Release note: None
craig bot
pushed a commit
to cockroachdb/cockroach
that referenced
this issue
Nov 3, 2023
113643: roachtest: move validate-after-version-upgrade to new framework r=rafiss a=rafiss The new framework provides a few more testing enhancements and is the only one that will be maintained. fixes #110535 Release note: None 113676: roachtest: fix js install command (gpg) r=rafiss a=annrpom We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: #113673 Fixes: #113662 Fixes: #113659 Fixes: #113675 Fixes: #113677 Fixes: #113762 Release note: None 113698: metamorphic: add MVCC{CheckFor,}AcquireLock operations r=nvanbenschoten a=itsbilal This change adds two new operations to the MVCC metamorphic testing package that were added in #110323. We check for determinism in the storage package by adding these operations to the metamorphic tests as well. Fixes #109650. Epic: none Release note: None Co-authored-by: Rafi Shamim <[email protected]> Co-authored-by: Annie Pompa <[email protected]> Co-authored-by: Bilal Akhtar <[email protected]>
blathers-crl bot
pushed a commit
to cockroachdb/cockroach
that referenced
this issue
Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: #113673 Fixes: #113662 Fixes: #113659 Release note: None
blathers-crl bot
pushed a commit
to cockroachdb/cockroach
that referenced
this issue
Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: #113673 Fixes: #113662 Fixes: #113659 Release note: None
blathers-crl bot
pushed a commit
to cockroachdb/cockroach
that referenced
this issue
Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: #113673 Fixes: #113662 Fixes: #113659 Release note: None
blathers-crl bot
pushed a commit
to cockroachdb/cockroach
that referenced
this issue
Nov 7, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: #113673 Fixes: #113662 Fixes: #113659 Release note: None
rafiss
pushed a commit
to rafiss/cockroach
that referenced
this issue
Nov 7, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922. In case we are running into an issue with machines being reused, we first check to see if we can install nodejs and npm before we add a nodesource key and deb repository (to prevent gpg: dearmoring failed: File exists) issues. (Copied from a reply to the bug report in the issue linked above) > For any script use you should anyway use --batch which disables the use of the tty as a side-effect. Fixes: cockroachdb#113673 Fixes: cockroachdb#113662 Fixes: cockroachdb#113659 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue in docker build:
Info:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614
How to fix: I've added --no-tty to gpg
example:
The text was updated successfully, but these errors were encountered: