As title.
What am I doing?
Just trying to create my first hello world snap.
I created a first hello world with
snapcraft init
then I tried to build it with the
snapcraft
command.
It returns this error:
LXD requires additional permissions.
Recommended resolution: Ensure that the user is in the ‘lxd’ group.
Visit https://documentation.ubuntu.com/lxd/en/latest/getting_started/ for instructions on installing and configuring LXD for your operating system.
I tried adding my user to LXD but it doesn’t work. still have this error.
If I launch the snapcraft command with the sudo I have this error:
Timed out waiting for networking to be ready.
Full execution log: ‘/root/.local/state/snapcraft/log/snapcraft-20241127-115615.011560.log’
any idea on what is happening here?
ogra
November 27, 2024, 11:04am
2
Did you log out and back in again after adding your user to that group? If you don’t, the change won’t be active…
1 Like
I logged out and it didn’t worked, I rebooted and it worked. weird, but thanks
trying to create an hello world:
returns this error:
Timed out waiting for networking to be ready.
any idea?
Do you have docker installed?
yess but I don’t want to de-install it just for snapcraft.
I noticed that disabling ufw (ubuntu firewall) made the trick.
but what should I allow to permit to snapcraft to work with the firewall running using ubuntu 24.10 and ufw?
Hmmm… @zyga @sergiusens Can you please help him?
1 Like
ogra
November 27, 2024, 6:40pm
8
I think there are workarounds in the well known docker issue (that apparently won’t get fixed is to be fixed soon ! (after only 7 years ))
opened 11:03AM - 15 Sep 17 UTC
I am running a server with LXC containers on it.
I found a software that was av… ailable as Docker containers, so I installed Docker on the server and tried that software.
* [x] This is reporting unexpected problematic behaviour
* [x] This is a feature request
* [x] I searched existing issues before opening this one
### Expected behavior
Both LXC containers should work normally, and new Docker containers should work.
If it isn't possible for Docker to start a container without interrupting existing containers due to any conceptual issue, I would expect Docker to detect that such a problem exists and to provide an overridable error message or at least a warning, that it might interfere with existing containers.
### Actual behavior
The Docker containers work, but the LXC containers are suddenly disconnected from the network. The LXC containers are still running, and I can attach to them directly, but they aren't visible on the network anymore, they cannot be pinged, and their services aren't available anymore. Docker has disconnected the running LXC containers from the network.
### Steps to reproduce the behavior
Install Debian Linux
Install LXC
Create a LXC container with it's own IP address
Run a server on the LXC container
Install Docker
Download and run a Docker container
Try to access the server in the LXC container over the network
**Output of `docker version`:**
```
Client:
Version: 17.07.0-ce
API version: 1.31
Go version: go1.8.3
Git commit: 8784753
Built: Tue Aug 29 17:42:54 2017
OS/Arch: linux/amd64
Server:
Version: 17.07.0-ce
API version: 1.31 (minimum version 1.12)
Go version: go1.8.3
Git commit: 8784753
Built: Tue Aug 29 17:41:44 2017
OS/Arch: linux/amd64
Experimental: false
```
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 4
Server Version: 17.07.0-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 42
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3addd840653146c90a254301d6c3a663c7fd6429
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.0-3-amd64
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 31.41GiB
Name: servername
ID: ZQY3:PKBB:X7ZY:WY54:VKG4:IILY:42LG:KURS:4MXC:JR67:A6IX:T3KT
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: http://proxy:8080/
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
```
```
**Additional environment details (AWS, VirtualBox, physical, etc.)**
Linux version 4.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)
1 Like
For people using Ubuntu this solved for me:
sudo ufw allow in on lxdbr0
sudo ufw route allow in on lxdbr0
sudo ufw route allow out on lxdbr0
1 Like