[ 
https://issues.apache.org/jira/browse/GEODE-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alberto Bustamante Reyes resolved GEODE-7263.
---------------------------------------------
    Resolution: Duplicate

> Geode Native: Dockerfile for building the user guide needs updating
> -------------------------------------------------------------------
>
>                 Key: GEODE-7263
>                 URL: https://issues.apache.org/jira/browse/GEODE-7263
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, native client
>            Reporter: Dave Barnes
>            Priority: Major
>
> We provide a Docker file for building the Native Client User Guide (
> geode-native/docs/docker
> ). When I follow README instructions, I get errors regarding unrecognized 
> addresses and out-of-date components. A sample:
> gpg: directory '/root/.gnupg' created
> gpg: keybox '/root/.gnupg/pubring.kbx' created
> gpg: keyserver receive failed: Cannot assign requested address
> gpg: keyserver receive failed: No data
> gpg: key 105BD0E739499BDB: 7 signatures not checked due to missing keys
> gpg: /root/.gnupg/trustdb.gpg: trustdb created
> gpg: key 105BD0E739499BDB: public key "Piotr Kuczynski 
> <piotr.kuczyn...@gmail.com>" imported
> gpg: key 3804BB82D39DC0E3: 106 signatures not checked due to missing keys
> gpg: key 3804BB82D39DC0E3: public key "Michal Papis (RVM signing) 
> <mpa...@gmail.com>" imported
> gpg: no ultimately trusted keys found
> gpg: Total number processed: 2
> gpg:               imported: 2
>  
> ...
> Step 6/13 : RUN /bin/bash -l -c "rvm requirements"
>  ---> Running in 10c01ef4a95e
> mesg: ttyname failed: Inappropriate ioctl for device
>  
> ...
> Please be aware that you just installed a ruby that requires 3 patches just 
> to be compiled on an up to date linux system.
> This may have known and unaccounted for security vulnerabilities.
> Please consider upgrading to ruby-2.6.5 which will have all of the latest 
> security patches.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to