SteveLTN/https-portal

/usr/lib/ruby/2.5.0/fileutils.rb:1291:in `initialize': No such file or directory @ rb_sysopen - /var/lib/https-portal/default_server/default_server.key (Errno::ENOENT)

deadshot465 opened this issue · 3 comments

deadshot465 commented

So I use a couple of docker containers alongside with https-portal with docker-compose.yml, and today after I did docker-compose pull and docker-compose up -d and https-portal pulled the latest 1.20.0 image, https-portal seemed to fail to start with the following error in the logs:

https-portal_1  | -----END DH PARAMETERS-----
https-portal_1  | RSA key ok
https-portal_1  | /usr/lib/ruby/2.5.0/fileutils.rb:1291:in `initialize': No such file or directory @ rb_sysopen - /var/lib/https-portal/default_server/default_server.key (Errno::ENOENT)
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:1291:in `open'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:1291:in `copy_file'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:432:in `copy_file'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:359:in `block in cp'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:1463:in `block in fu_each_src_dest'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:1479:in `fu_each_src_dest0'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:1461:in `fu_each_src_dest'
https-portal_1  | 	from /usr/lib/ruby/2.5.0/fileutils.rb:358:in `cp'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:101:in `block in ensure_keys_and_certs_exist'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:96:in `each'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:96:in `ensure_keys_and_certs_exist'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:35:in `block in setup_config'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:132:in `block in with_lock'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:130:in `open'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:130:in `with_lock'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:19:in `setup_config'
https-portal_1  | 	from /opt/certs_manager/certs_manager.rb:11:in `setup'
https-portal_1  | 	from /bin/setup:4:in `<main>'
https-portal_1  | [cont-init.d] 20-setup: exited 1.
https-portal_1  | [cont-finish.d] executing container finish scripts...
https-portal_1  | [cont-finish.d] done.
https-portal_1  | [s6-finish] waiting for services.
https-portal_1  | [s6-finish] sending all processes the TERM signal.

Nothing changed in my docker-compose.yml and it has worked nicely until it got upgraded to 1.20.0. I'm considering reverting back to the previous version to give it a try, but is this a possible bug in the latest version?

SteveLTN commented

Oops...
Please revert to 1.19 for now. I'm making a hotfix right way.

  • 👍1
SteveLTN commented

I released 1.20.1. Sorry for my mistake!

deadshot465 commented

No worries. Tested without any problem now.
Thank you for the fast response!