Can't build image - Githubissues

JuniorJPDJ commented 6 years ago

Errors: for apt update after adding repository

Reading package lists...
W: GPG error: http://cdn-fastly.deb.debian.org/debian jessie Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553  NO_PUBKEY 7638D0442B90D010  NO_PUBKEY CBF8D6FD518E17E1
W: The repository 'http://httpredir.debian.org/debian jessie Release' is not signed.
Reading package lists...

for adduser <lolwtf?>

Step 14/55 : RUN adduser --quiet --disabled-password --uid 1000 --home /home/botmaster --shell /bin/bash botmaster
 ---> Running in 580bce5b003d
Changing the user information for botmaster
Enter the new value, or press ENTER for the default
    Full Name []:   Room Number []:     Work Phone []:  Home Phone []:  Other []: Use of uninitialized value $answer in chop at /usr/sbin/adduser line 621.
Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 622.
Is the information correct? [Y/n] Removing intermediate container 580bce5b003d

and error, which killed my build, no key in keyserver:

Step 21/55 : RUN gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
 ---> Running in 785c84e89adb
gpg: directory `/home/botmaster/.gnupg' created
gpg: new configuration file `/home/botmaster/.gnupg/gpg.conf' created
gpg: WARNING: options in `/home/botmaster/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/home/botmaster/.gnupg/secring.gpg' created
gpg: keyring `/home/botmaster/.gnupg/pubring.gpg' created
gpg: requesting key D39DC0E3 from hkp server keys.gnupg.net
gpgkeys: key 409B6B1796C275462A1703113804BB82D39DC0E3 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver helper general error
gpg: keyserver communications error: unknown pubkey algorithm
gpg: keyserver receive failed: unknown pubkey algorithm
The command '/bin/sh -c gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3' returned a non-zero code: 2

Natenom commented 6 years ago

When I run the following command on my local machine it works. So the key is still there.

gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3

gpg: directory '/home/test/.gnupg' created gpg: keybox '/home/test/.gnupg/pubring.kbx' created gpg: /home/test/.gnupg/trustdb.gpg: trustdb created gpg: key 3804BB82D39DC0E3: public key "Michal Papis (RVM signing) mpapis@gmail.com" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1

Natenom commented 6 years ago

The error for apt occurs too on my test server but you can ignore it as packages are installed with --force ... if I remember correctly. Not the best way but it works.

Natenom commented 6 years ago

Also the error for adding user occurs but the docker image can still be built.

Natenom commented 6 years ago

I just rebuild the complete image (without cache) for the bots on our server and all three bots are running.

JuniorJPDJ commented 6 years ago

I also built it on other machine, and it's working great. What?! >__<

MusicGenerator / mumble-ruby-pluginbot-docker

Can't build image #9