Skip to content
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

bug: Ubuntu Podman - /run/nanocl/nanocl.sock: Connector has been disconnected #1189

Open
lsabi opened this issue Dec 22, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@lsabi
Copy link

lsabi commented Dec 22, 2024

Describe the bug
After a clean install of Ubuntu Server 24.04, followed the tutorial but I'm not able to run anything. nanocl is installed (seems correctly).

To Reproduce
Steps to reproduce the behavior:
Followed the tutorial for installation by adding the .deb package repository and creating the usergroup

Installed component for podman with sudo nanocl install --docker-host unix:///var/run/podman/podman.sock.
Output is:

> cargo/nstore (running)
> cargo/nmetrics (running)
> cargo/nproxy (running)
> cargo/ncproxy (running)
> cargo/ndns (running)
> cargo/ncdns (running)
> cargo/ndaemon (running)
Nanocl system installed

When checking version I get

nanocl version

=== [nanocli] ===
Arch: x86_64
Channel: stable
Version: 0.16.2
Commit ID: 9574061c53c0e74bd4837fb6a7708da73077681e
/run/nanocl/nanocl.sock: Connector has been disconnected

Expected behavior
Expecting the connector to work.

Desktop (please complete the following information):

  • OS: Linux
  • Distribution: Ubuntu Server
  • Version 24.04

Additional context
Podman has been installed from the default repo

podman --version
podman version 4.9.3
@lsabi lsabi added the bug Something isn't working label Dec 22, 2024
@leon3s
Copy link
Member

leon3s commented Jan 2, 2025

Hey thanks for the bug report, the podman support is not as good as expected, right now it's best to use docker.. see: #1009

I'll make it fully compatible at some point, but being able to change the runtime is not a priority right now. I'm focusing on the cluster fonctionallity

@lsabi
Copy link
Author

lsabi commented Jan 2, 2025

I saw the issue, but thought that podman compatibility was fixed and stable.

Ok, not a problem, I'll reinstall and connect docker instead. A warning on the docs might reduce the number of people asking for help/support though.

Looking forward seeing and testing the cluster functionality, as k8s is quite of a hassle to maintain. Thanks for the work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants