Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

RPM installation fails #709

Closed
opichon opened this issue Feb 5, 2016 · 5 comments
Closed

RPM installation fails #709

opichon opened this issue Feb 5, 2016 · 5 comments

Comments

@opichon
Copy link

opichon commented Feb 5, 2016

ln -s '/usr/lib/systemd/system/portus_crono.service' '/etc/systemd/system/multi-user.target.wants/portus_crono.service'
ln -s '/usr/lib/systemd/system/apache2.service' '/etc/systemd/system/httpd.service'
ln -s '/usr/lib/systemd/system/apache2.service' '/etc/systemd/system/apache.service'
ln -s '/usr/lib/systemd/system/apache2.service' '/etc/systemd/system/multi-user.target.wants/apache2.service'
Failed to execute operation: No such file or directory
/srv/Portus/packaging/suse/portusctl/lib/runner.rb:7:in exec': Something went wrong while invoking: systemctl enable registry (RuntimeError) from /srv/Portus/packaging/suse/portusctl/lib/runner.rb:30:inactivate_service'
from /srv/Portus/packaging/suse/portusctl/lib/configurator.rb:179:in block in services' from /srv/Portus/packaging/suse/portusctl/lib/configurator.rb:178:ineach'
from /srv/Portus/packaging/suse/portusctl/lib/configurator.rb:178:in services' from /srv/Portus/packaging/suse/portusctl/lib/cli.rb:91:insetup'
from /srv/Portus/vendor/bundle/ruby/2.1.0/gems/thor-0.18.1/lib/thor/command.rb:27:in run' from /srv/Portus/vendor/bundle/ruby/2.1.0/gems/thor-0.18.1/lib/thor/invocation.rb:120:ininvoke_command'
from /srv/Portus/vendor/bundle/ruby/2.1.0/gems/thor-0.18.1/lib/thor.rb:363:in dispatch' from /srv/Portus/vendor/bundle/ruby/2.1.0/gems/thor-0.18.1/lib/thor/base.rb:439:instart'
from packaging/suse/portusctl/bin/portusctl:5:in `

'
i

I used this command:

portusctl setup --local-registry

Does this imply that the registry must already be installed and running before running the portusctl setup command? The documentation seems to imply that it will install the docker registry as part of the portus setup.

@opichon
Copy link
Author

opichon commented Feb 5, 2016

It appears to work if the docker registry is installed separately before installing portus. You may want to make the documentation slightly less confusing.

@opichon opichon closed this as completed Feb 5, 2016
@mssola
Copy link
Collaborator

mssola commented Feb 5, 2016

The "Portus' dependencies" section says

(that’s why the RPM just recommends these packages, instead of requiring them)

But you're right that we could have phrased the whole section in a more direct and clear way. I'll take a look at it. Thanks.

@flavio
Copy link
Member

flavio commented Feb 5, 2016

@mssola we should also change portusctl to print some warning when --local-registry is passed and the registry package is not found.

@flavio
Copy link
Member

flavio commented Feb 5, 2016

@mssola I would reopen this issue and change the title accordingly. What do you think?

@flavio
Copy link
Member

flavio commented Feb 5, 2016

@mssola I would reopen this issue and change the title accordingly. What do you think?

Ignore me, I've just seen issue #711

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants