Comments (83)
mkinney
commented on July 24, 2024
2
I've tried using docker on Centos7 with this:
docker run -d -p 8000:8000 alpine ash -c "while true; do echo hello world; sleep 1; done"
and it does not throw the error that happens on Ubuntu. I'm going to see if I can build Nightfall on Centos7.
from nightfall.
Solexplorer
commented on July 24, 2024
1
Ok, I am going to try with a user
from nightfall.
mkinney
commented on July 24, 2024
1
@aj-may Thanks for that, but same behavior.
# apparmor_status
apparmor module is loaded.
16 profiles are loaded.
16 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/lxc-start
/usr/bin/man
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/NetworkManager/nm-dhcp-helper
/usr/lib/connman/scripts/dhclient-script
/usr/lib/snapd/snap-confine
/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
/usr/sbin/tcpdump
docker-default
lxc-container-default
lxc-container-default-cgns
lxc-container-default-with-mounting
lxc-container-default-with-nesting
man_filter
man_groff
0 profiles are in complain mode.
16 processes have profiles defined.
16 processes are in enforce mode.
docker-default (3379)
docker-default (3419)
docker-default (3435)
docker-default (3438)
docker-default (3440)
docker-default (3442)
docker-default (3443)
docker-default (3446)
docker-default (3637)
docker-default (3638)
docker-default (3639)
docker-default (3640)
docker-default (3641)
docker-default (3642)
docker-default (3643)
docker-default (3644)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
service apparmor stop
service apparmor teardown
# apparmor_status
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
I see selinux is not applicable.
I've disabled the firewall (ufw).
I flushed iptables.
Any other ideas?
For now, I'm building a centos box to see if it is OS specific.
from nightfall.
Westlad
commented on July 24, 2024
1
@Solexplorer Other people report problems with docker-proxy on Linux. It's possible you have this problem: the error seems no longer to be directly within the nightfall code base. As soon as I get time (hopefully this week) I'm going to try dory as an alternative to docker-proxy on Linux, which was recommended to me. If you're able to try in the meantime please let me know how you get on. See issue #20
I can run on a 16GB Mac so you should be fine with 32GB. For me 12GB memory and 4GB swap works ok, without taking over the whole machine
from nightfall.
mkinney
commented on July 24, 2024
1
I'm still at it...
looks like apparmor is used somehow
docker info | grep -B1 app
Security Options:
apparmor
Here is how I can get more info as to why it might be failing...
put docker into debug mode
cat /etc/docker/daemon.json
{
"debug": true,
"ipv6": false
}
systemctl restart docker
added "-vv" to args in /etc/default/networkd-dispatcher
cat /etc/default/networkd-dispatcher
# Specify command line options here. This config file is used
# by the included systemd service file.
networkd_dispatcher_args="--run-startup-triggers -vv "
systemctl restart networkd-dispatcher
Now I see some info:
Jun 6 04:04:58 three systemd-timesyncd[601]: Network configuration changed, trying to establish connection.
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AdministrativeState'): dbus.String('unmanaged', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_320')
Jun 6 04:04:58 three networkd-dispatcher[4337]: WARNING:Unknown index 20 seen, reloading interface list
Jun 6 04:04:58 three kernel: [ 1618.285964] docker0: port 1(veth689303e) entered blocking state
Jun 6 04:04:58 three kernel: [ 1618.285968] docker0: port 1(veth689303e) entered disabled state
Jun 6 04:04:58 three kernel: [ 1618.286117] device veth689303e entered promiscuous mode
Jun 6 04:04:58 three kernel: [ 1618.286271] IPv6: ADDRCONF(NETDEV_UP): veth689303e: link is not ready
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.628194370Z" level=debug msg="Assigning addresses for endpoint http-proxy's interface on network bridge"
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Performed interface scan; state: <Dispatcher({'iface_names_by_idx': {1: 'lo', 2: 'eth0', 16: 'docker0', 19: 'vethd4816a4', 20: 'veth689303e'}, 'ifaces_by_name': {'lo': NetworkctlListState(idx=1, name='lo', type='loopback', operational='carrier', administrative='unmanaged'), 'eth0': NetworkctlListState(idx=2, name='eth0', type='ether', operational='routable', administrative='configured'), 'docker0': NetworkctlListState(idx=16, name='docker0', type='ether', operational='no-carrier', administrative='unmanaged'), 'vethd4816a4': NetworkctlListState(idx=19, name='vethd4816a4', type='ether', operational='off', administrative='unmanaged'), 'veth689303e': NetworkctlListState(idx=20, name='veth689303e', type='ether', operational='no-carrier', administrative='unmanaged')}, 'script_dir': '/etc/networkd-dispatcher:/usr/lib/networkd-dispatcher'})>
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:No change represented by administrative state 'unmanaged' for interface 'veth689303e'
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('OperationalState'): dbus.String('no-carrier', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_320')
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:No change represented by operational state 'no-carrier' for interface 'veth689303e'
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AdministrativeState'): dbus.String('unmanaged', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_319')
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:No change represented by administrative state 'unmanaged' for interface 'vethd4816a4'
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.637891423Z" level=debug msg="Programming external connectivity on endpoint http-proxy (9367c7aa7e4b36817439499421cab26a5895f4ab309c6c11e629f3daac995ac4)"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.638085946Z" level=debug msg="/sbin/iptables, [--wait -t nat -C DOCKER -p udp -d 0/0 --dport 19322 -j DNAT --to-destination 172.17.0.2:19322 ! -i docker0]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.641901101Z" level=debug msg="/sbin/iptables, [--wait -t nat -A DOCKER -p udp -d 0/0 --dport 19322 -j DNAT --to-destination 172.17.0.2:19322 ! -i docker0]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.643828018Z" level=debug msg="/sbin/iptables, [--wait -t filter -C DOCKER ! -i docker0 -o docker0 -p udp -d 172.17.0.2 --dport 19322 -j ACCEPT]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.645528304Z" level=debug msg="/sbin/iptables, [--wait -t filter -A DOCKER ! -i docker0 -o docker0 -p udp -d 172.17.0.2 --dport 19322 -j ACCEPT]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.647141858Z" level=debug msg="/sbin/iptables, [--wait -t nat -C POSTROUTING -p udp -s 172.17.0.2 -d 172.17.0.2 --dport 19322 -j MASQUERADE]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.648757781Z" level=debug msg="/sbin/iptables, [--wait -t nat -A POSTROUTING -p udp -s 172.17.0.2 -d 172.17.0.2 --dport 19322 -j MASQUERADE]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.658879346Z" level=debug msg="/sbin/iptables, [--wait -t nat -C DOCKER -p udp -d 0/0 --dport 19322 -j DNAT --to-destination 172.17.0.2:19322 ! -i docker0]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.660773630Z" level=debug msg="/sbin/iptables, [--wait -t nat -D DOCKER -p udp -d 0/0 --dport 19322 -j DNAT --to-destination 172.17.0.2:19322 ! -i docker0]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.662557548Z" level=debug msg="/sbin/iptables, [--wait -t filter -C DOCKER ! -i docker0 -o docker0 -p udp -d 172.17.0.2 --dport 19322 -j ACCEPT]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.664318476Z" level=debug msg="/sbin/iptables, [--wait -t filter -D DOCKER ! -i docker0 -o docker0 -p udp -d 172.17.0.2 --dport 19322 -j ACCEPT]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.666033412Z" level=debug msg="/sbin/iptables, [--wait -t nat -C POSTROUTING -p udp -s 172.17.0.2 -d 172.17.0.2 --dport 19322 -j MASQUERADE]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.667637686Z" level=debug msg="/sbin/iptables, [--wait -t nat -D POSTROUTING -p udp -s 172.17.0.2 -d 172.17.0.2 --dport 19322 -j MASQUERADE]"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.669274319Z" level=warning msg="Failed to allocate and map port 19322-19322: Error starting userland proxy: "
Jun 6 04:04:58 three kernel: [ 1618.343087] docker0: port 1(veth689303e) entered disabled state
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('OperationalState'): dbus.String('off', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_320')
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=20, name='veth689303e', type='ether', operational='off', administrative='unmanaged') entering state 'off': no triggers
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AdministrativeState'): dbus.String('linger', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_319')
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Path '/etc/networkd-dispatcher/linger.d' does not exist; skipping
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Path '/usr/lib/networkd-dispatcher/linger.d' does not exist; skipping
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=19, name='vethd4816a4', type='ether', operational='off', administrative='linger') entering state 'linger': no triggers
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AdministrativeState'): dbus.String('linger', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_320')
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Path '/etc/networkd-dispatcher/linger.d' does not exist; skipping
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Path '/usr/lib/networkd-dispatcher/linger.d' does not exist; skipping
Jun 6 04:04:58 three networkd-dispatcher[4337]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=20, name='veth689303e', type='ether', operational='off', administrative='linger') entering state 'linger': no triggers
Jun 6 04:04:58 three kernel: [ 1618.350592] device veth689303e left promiscuous mode
Jun 6 04:04:58 three kernel: [ 1618.350601] docker0: port 1(veth689303e) entered disabled state
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.717976849Z" level=debug msg="Releasing addresses for endpoint http-proxy's interface on network bridge"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.718068620Z" level=debug msg="ReleaseAddress(LocalDefault/172.17.0.0/16, 172.17.0.2)"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.718122424Z" level=debug msg="Released address PoolID:LocalDefault/172.17.0.0/16, Address:172.17.0.2 Sequence:App: ipam/default/data, ID: LocalDefault/172.17.0.0/16, DBIndex: 0x0, Bits: 65536, Unselected: 65532, Sequence: (0xe0000000, 1)->(0x0, 2046)->(0x1, 1)->end Curr:3"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.733669444Z" level=warning msg="d5f1d3ccd23cc7705c73828966723e447ec66796991bbdf2e00b25a9742bad3e cleanup: failed to unmount IPC: umount /var/lib/docker/containers/d5f1d3ccd23cc7705c73828966723e447ec66796991bbdf2e00b25a9742bad3e/mounts/shm, flags: 0x2: no such file or directory"
Jun 6 04:04:58 three systemd-timesyncd[601]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com).
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.765909549Z" level=error msg="d5f1d3ccd23cc7705c73828966723e447ec66796991bbdf2e00b25a9742bad3e cleanup: failed to delete container from containerd: no such container"
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.765974455Z" level=debug msg="FIXME: Got an API for which error does not match any expected type!!!: driver failed programming external connectivity on endpoint http-proxy (9367c7aa7e4b36817439499421cab26a5895f4ab309c6c11e629f3daac995ac4): Error starting userland proxy: " error_type=types.internal module=api
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.765999563Z" level=error msg="Handler for POST /v1.40/containers/d5f1d3ccd23cc7705c73828966723e447ec66796991bbdf2e00b25a9742bad3e/start returned error: driver failed programming external connectivity on endpoint http-proxy (9367c7aa7e4b36817439499421cab26a5895f4ab309c6c11e629f3daac995ac4): Error starting userland proxy: "
Jun 6 04:04:58 three dockerd[3997]: time="2019-06-06T04:04:58.766022369Z" level=debug msg="FIXME: Got an API for which error does not match any expected type!!!: driver failed programming external connectivity on endpoint http-proxy (9367c7aa7e4b36817439499421cab26a5895f4ab309c6c11e629f3daac995ac4): Error starting userland proxy: " error_type=types.internal module=api
from nightfall.
mkinney
commented on July 24, 2024
1
Ok. It was a stupid thing. There is a binary called docker-proxy in /usr/bin.
[root@centos ~]# file /usr/bin/docker-proxy
/usr/bin/docker-proxy: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=c4a4d4ea5debe878fffe3b9b27d6a1fdfa74c800, not stripped
So, these are the installation steps (note the 2nd one):
cd /usr/local/bin && curl -sL https://raw.githubusercontent.com/aj-may/docker-proxy/master/install.sh | bash
mv /usr/local/bin/docker-proxy /usr/local/bin/docker-proxy2
The proxy stuff works.
[root@centos bin]# docker-proxy2 start
Proxy image not found. Pulling image...
latest: Pulling from codekitchen/dinghy-http-proxy
4fe2ade4980c: Pull complete
c691664ebb08: Pull complete
a6f6a50701b6: Pull complete
5980ba3b5a39: Pull complete
b69c20bf637c: Pull complete
c72f60b533b1: Pull complete
74c87e1ef027: Pull complete
90088574b3dd: Pull complete
bb8452179351: Pull complete
c11e15b24bed: Pull complete
4c394a654280: Pull complete
b999afd9172f: Pull complete
96c9e2e9658f: Pull complete
ab93cf1dee12: Pull complete
e855c57f80fc: Pull complete
4a9d70dee7c7: Pull complete
de1ba7623018: Pull complete
Digest: sha256:d372f277754e06c8b642d2ed1e446100d2aa9d8b02ffbdf9482b4f406f162d17
Status: Downloaded newer image for codekitchen/dinghy-http-proxy:latest
Starting container...
/etc/resolver/docker does not exist. Creating... (this will prompt for password)
sudo: killall: command not found
[root@centos bin]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7b4b1d842a66 codekitchen/dinghy-http-proxy "/app/docker-entrypo…" 4 seconds ago Up 4 seconds 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 19322/tcp, 0.0.0.0:19322->19322/udp http-proxy
Ugh. That took me longer than it should have to figure out.
from nightfall.
Solexplorer
commented on July 24, 2024
1
@mkinney Thank you !!
It's working right now, Congratulations !
from nightfall.
Solexplorer
commented on July 24, 2024
1
I am running on Ubuntu and it compiled successfully with 32GB ram
from nightfall.
mkinney
commented on July 24, 2024
1
I'll switch to 32gb ram and 64gb swap.
from nightfall.
Solexplorer
commented on July 24, 2024
1
@mkinney I had the same issue and switching to a non-root user solved the issue
from nightfall.
mkinney
commented on July 24, 2024
1
Hey! It built the ft-burn one successfully. Will let this one build to see if it works.
from nightfall.
mkinney
commented on July 24, 2024
1
Seeing the same thing. Not sure. Will do some poking around, but it will have to be later. Please share if you figure it out.
from nightfall.
mkinney
commented on July 24, 2024
1
ok to close issue?
;-)
from nightfall.
iAmMichaelConnor
commented on July 24, 2024
This error is indicative of the ZoKrates docker container ‘falling over’ due to insufficient resources being allocated to Docker.
Please check ‘docker stats’ to see the maximum amount of RAM which is being allocated to those containers. (Paste the output here if you’re unsure).
from nightfall.
Solexplorer
commented on July 24, 2024
@iAmMichaelConnor
I am running on a server with 30GB and by default containers have no resource limit so they should be able to use all the memory if I am correct.
Here's the output:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
7fc47e11c9ea pensive_benz 0.01% 4.711MiB / 30.68GiB 0.01% 2.83kB / 0B 0B / 0B 1
4b3643548fea hungry_wright 0.01% 1.617MiB / 30.68GiB 0.01% 2.83kB / 0B 0B / 0B 1
d453c11b3142 hungry_bhaskara 0.01% 4.586MiB / 30.68GiB 0.01% 2.9kB / 0B 0B / 0B 1
308774e557ce brave_bassi 0.01% 7.934MiB / 30.68GiB 0.03% 2.9kB / 0B 0B / 0B 1
9cc8fa237611 vigilant_khayyam 0.01% 1.547MiB / 30.68GiB 0.00% 2.9kB / 0B 0B / 0B 1
b76c40d06ab0 trusting_elion 0.01% 4.574MiB / 30.68GiB 0.01% 2.9kB / 0B 0B / 0B 1
cfab6a044f20 trusting_carson 0.01% 4.57MiB / 30.68GiB 0.01% 2.97kB / 0B 0B / 0B 1
01dc852a4baa infallible_snyder 0.00% 1.766MiB / 30.68GiB 0.01% 2.97kB / 0B 0B / 0B 1
4f74fb357697 frosty_torvalds 0.01% 4.477MiB / 30.68GiB 0.01% 3.04kB / 0B 0B / 0B 1
3234a2650e53 jovial_mestorf 0.01% 7.824MiB / 30.68GiB 0.02% 3.18kB / 0B 0B / 0B 1
f4ef8e670c6a vibrant_jennings 0.01% 1.613MiB / 30.68GiB 0.01% 3.18kB / 0B 0B / 0B 1
51bd7322c597 jovial_kirch 0.00% 4.422MiB / 30.68GiB 0.01% 4.11kB / 0B 0B / 0B 1
When I run npm run setup-all:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
bb93c148e166 wizardly_gagarin 0.06% 1.966GiB / 30.68GiB 6.41% 726B / 0B 0B / 0B 2
7fc47e11c9ea pensive_benz 0.83% 4.711MiB / 30.68GiB 0.01% 2.9kB / 0B 0B / 0B 1
4b3643548fea hungry_wright 0.08% 1.617MiB / 30.68GiB 0.01% 2.83kB / 0B 0B / 0B 1
d453c11b3142 hungry_bhaskara 0.78% 4.586MiB / 30.68GiB 0.01% 2.9kB / 0B 0B / 0B 1
308774e557ce brave_bassi 1.66% 7.934MiB / 30.68GiB 0.03% 2.97kB / 0B 0B / 0B 1
9cc8fa237611 vigilant_khayyam 0.07% 1.547MiB / 30.68GiB 0.00% 2.9kB / 0B 0B / 0B 1
b76c40d06ab0 trusting_elion 0.77% 4.574MiB / 30.68GiB 0.01% 2.9kB / 0B 0B / 0B 1
cfab6a044f20 trusting_carson 0.82% 4.57MiB / 30.68GiB 0.01% 3.04kB / 0B 0B / 0B 1
01dc852a4baa infallible_snyder 0.07% 1.766MiB / 30.68GiB 0.01% 2.97kB / 0B 0B / 0B 1
4f74fb357697 frosty_torvalds 0.78% 4.477MiB / 30.68GiB 0.01% 3.04kB / 0B 0B / 0B 1
3234a2650e53 jovial_mestorf 1.72% 7.824MiB / 30.68GiB 0.02% 3.18kB / 0B 0B / 0B 1
f4ef8e670c6a vibrant_jennings 0.08% 1.613MiB / 30.68GiB 0.01% 3.18kB / 0B 0B / 0B 1
51bd7322c597 jovial_kirch 0.88% 4.422MiB / 30.68GiB 0.01% 4.11kB / 0B 0B / 0B 1
from nightfall.
Westlad
commented on July 24, 2024
Hi @Solexplorer are you getting problems with just nft-transfer? Do ft-burn, ft-transfer and ft-mint etc work ok? The automated script runs those first.
from nightfall.
Solexplorer
commented on July 24, 2024
@Westlad I've tried to move all the nft to another folder outside of the nightfall repo but I still get the error.
I've tried also to run only ft-burn and it's giving me the same error, now I am thinking how is that possible if I have 30 Gb as memory ?
from nightfall.
Solexplorer
commented on July 24, 2024
I tried to delete the repo and start everything from the beginning but it still stucks at the same point:
Here is the command: root@ubuntu-32gb-fsn1-1:~/nightfall/zkp# npm run setup-all
And here is the error log:
num constraints: 1157594
num inputs: 7
�
�* SAP number of variables: 2245787
* SAP pre degree: 1157594
* SAP degree: 2359296
* SAP number of input variables: 7
* G window: 20
* H_gamma window: 17
* G1 elements in PK: 9096656
* G2 elements in PK: 2245789
* PK size in bits: 3462753881
* G1 elements in VK: 10
* G2 elements in VK: 3
* VK size in bits: 4077
vk.H = [0x210503b609828cd0d99b4222e7c8be53a47be87f7a9d00bd32dd39574aa619f8, 0x7e25944387a410fc95a6b1e674a930c487b57db04c74bd5ea7102d4a16de5de], [0x14f913151f43d10358ee704bcdfe541d7a8e538592067af248976678646b23c8, 0x72307c07ab3bd91b50ebe612d2400b6d3619ef22e2a10ec69d88ce49eb4d543]
vk.Galpha = 0x21d888288218a90ee1f9c031c7919477ec44bdf6da7f0e6cc144f1c75e8cd997, 0x9cd0185f398afc5d0ff629d34551a8819e1b803fe60501988bca22de4e84622
vk.Hbeta = [0xf94fea22a03fbfdb9f93230ae5245e130a609cb793e329c70c652b55e54974, 0x2338779c07fe080d4de946358b8274191d953361acdc43956e57175c913ec1ee], [0xd71a0df1d24e7aeaad4b50ff64c11ec461bb3740cad20a7cc1485804cee3492, 0x28f584bca1fdc86e1a4f4a3b7083db4003d7dc9d147f9bc43801a6eb993313a9]
vk.Ggamma = 0x17731dd6aa9cefa2ca7a7b1223de6369f107071ed70a4ffebd7bbc5d4b071e6b, 0x2db0b4985f2fc393e7d2613e61f0541f2d74ec481002c23d6db3821b286ff032
vk.Hgamma = [0x1a18c1a2a652c1c0ffc98cc51471be65175b60b05be2064784d136b925a95ca7, 0x139430dc73952629c04cf23e49b726219c7ee2f196915622d3c650a161728544], [0x29e9cb13fe409e3c14b197f4a405bac34786c5947f4450041b38f32562f129b8, 0x176e8abeed74d0e75efb086fcf73541b01a012bcefb442cfc22ed2a58bef9f27]
vk.query.len() = 8
vk.query[0] = 0x190e8389d207fe3f0d23453f0e1b237c27df9a9694ae35049e8307c57a798374, 0x2ddce5292dcadd18662b15b842b4374ec399b80b908b31edd95569a4943c8106
vk.query[1] = 0x285f4b9caf471645544a4125ef4c727d7955acb4273c288e99650d24ccb545ce, 0x11df646de1723293bd773cf87558692f729cbf7290c0b7959bbbd16e11ba923b
vk.query[2] = 0x27b093b01cefd42adbd6d208d448f8d1a2f887516ae5f084d2695f54e8e0a5cf, 0x2c4028ebc79e7709dee0fc9b0d1aac71d36c5b4379b62a0cc88a46c8ab112ee4
vk.query[3] = 0x86e6ff0f600c5ce1e83f9bc2b43406d6cb98b3f2e0d377b8c9074bd513f6f4c, 0x2dabaaf48944cd9a2f8a2bb4010c0129f855858d46c4d620727ad4c04194efa7
vk.query[4] = 0x20cdc1e3d0a5cbec0f8c80bd3ad6eb75ee303245d8f6200c52098cc1ec4b8705, 0x19e2916196a3c1ddb159ff21d3b39600da7f14a238d6b11fdaa2d2e4dbd2c8a5
vk.query[5] = 0x1f336896ce3fb11babb0bc8f4a9667600043a19e4826da4d6c9374820f65ae30, 0x1bb27949e9202f404821254563c0fdbfa67463e80cca06f1ede85259e9e37640
vk.query[6] = 0x25ae09c57fcf807b4d1a239302759c12ed1e280b56c26eddd4a3889b6ee84129, 0x1726dd51fe9ef5c6f885e14d79bf50589188fb50905d74058eb592ba7111a23
vk.query[7] = 0x15f3bb221f0f9f730577956147916b7536aec1560fd4d0b17655d06bdd0135c5, 0x23eb9c05e9e5ad78882a5aa7009b9feedd28a2d88e953dcfb2b5d263f3340022
}
� �setup successful: true
SETUP MESSAGE: SETUP COMPLETE
Export Verifier nft-transfer ...
� �Exporting verifier...
� �Finished exporting verifier.
nft-transfer SETUP MESSAGE: EXPORT-VERIFIER COMPLETE
� ��cp: cannot create regular file '/home/zokrates/code/out': Permission denied
cp: cannot create regular file '/home/zokrates/code/out.code': Permission denied
cp: cannot create regular file '/home/zokrates/code/proving.key': Permission denied
cp: cannot create regular file '/home/zokrates/code/verification.key': Permission denied
cp: cannot create regular file '/home/zokrates/code/variables.inf': Permission denied
� Ucp: cannot create regular file '/home/zokrates/code/verifier.sol': Permission denied
nft-transfer SETUP MESSAGE: FILES COPIED TO THE MOUNTED DIR WITHIN THE CONTAINER. THE FILES WILL NOW ALSO EXIST WITHIN YOUR LOCALHOST'S FOLDER: /root/nightfall/zkp/code/gm17/nft-transfer/
Key extraction nft-transfer ...
{ Error: ENOENT: no such file or directory, open '/root/nightfall/zkp/code/gm17/nft-transfer/verifier.sol'
at Object.openSync (fs.js:438:3)
at Object.readFileSync (fs.js:343:35)
at Object.readFileSync (/root/nightfall/zkp/code/tools-key-extractor.js:18:6)
at keyExtractor (/root/nightfall/zkp/code/index.js:249:41)
at process._tickCallback (internal/process/next_tick.js:68:7)
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/root/nightfall/zkp/code/gm17/nft-transfer/verifier.sol' }
******************************************************************************************************************
Trusted setup has failed for nft-transfer.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
I don't know what verifier.sol is but Id on't even find it in this path :
path: '/root/nightfall/zkp/code/gm17/nft-transfer/verifier.sol'
May it be the fact that I am running everything using root ?
As far as I know, by default docker will use all the memory allocated, so it shouldn't be this the issue.
I am running docker version 18.09.6
from nightfall.
Westlad
commented on July 24, 2024
Hi @Solexplorer thanks for the info. I doubt this is a docker memory problem. Can you confirm a few things please:
- you didn't use
npm install(usenpm ciinstead) - if you did pleasegit reset --hardand start again with the README.md - you ran
npm run setup-allfrom thezkp/directory, not from the root of the repo?
from nightfall.
Westlad
commented on July 24, 2024
Actually, looking at your new output it seems that docker doesn't have permissions to write into the folders mounted in the docker container. I'm not sure why that would be but I can see that it's generating a proof just fine, the problem comes when the docker container tries to write into your directory tree. I see you are running as root. We don't normally do that. Could it be that these folders are read-only for the docker container? The docker container can't write to them and this may be the problem. Try running as a normal user rather than root and check the directory permissions.
from nightfall.
Solexplorer
commented on July 24, 2024
Hi @Westlad I can confirm you that I used npm ci and that I am running it in the zkp path: root@ubuntu-32gb-fsn1-1:~/nightfall/zkp#
from nightfall.
Solexplorer
commented on July 24, 2024
I've tried using a non-root user but now it doesn't even compile those files it jumps straight to the error.
I've deployed a new machine with 30GB and I have done the following:
- Installed docker
- Installed node 10.15.3
- npm ci and run npm run setup-all
Here is the log output now after npm run setup-all:
codeFile: ft-burn.code
outputDirPath: /home/rasholo/nightfall/zkp/code/gm17/ft-burn/
backend: gm17
a: null
ZoKrates running with Nodejs environment setup
Running the container; mounted: /home/rasholo/nightfall/zkp/code/gm17/ft-burn/:/home/zokrates/code/:cached
{ Error: connect EACCES /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
errno: 'EACCES',
code: 'EACCES',
syscall: 'connect',
address: '/var/run/docker.sock' }
Container running for ft-burn
TypeError: Cannot read property 'id' of undefined
at id (/home/rasholo/nightfall/zkp/code/index.js:139:68)
at process._tickCallback (internal/process/next_tick.js:68:7)
******************************************************************************************************************
Trusted setup has failed for ft-burn.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
Found existing files: [ 'ft-mint.code', 'ft-mint.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/ft-mint
If you continue, these files will be deleted (except for the '.pcode' file and any '.code' dependencies).
? Continue with the trusted setup? y/n y
Files remaining: [ 'ft-mint.code', 'ft-mint.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/ft-mint
Filing checks for codeFile: ft-mint.pcode
/home/rasholo/nightfall/zkp/code/gm17/ft-mint/ft-mint.pcode was copied to safe-dump/ft-mint.pcode
Checking for 'import' files in the .code file ft-mint
codeFileName: ft-mint
codeFile: ft-mint.code
outputDirPath: /home/rasholo/nightfall/zkp/code/gm17/ft-mint/
backend: gm17
a: null
ZoKrates running with Nodejs environment setup
Running the container; mounted: /home/rasholo/nightfall/zkp/code/gm17/ft-mint/:/home/zokrates/code/:cached
{ Error: connect EACCES /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
errno: 'EACCES',
code: 'EACCES',
syscall: 'connect',
address: '/var/run/docker.sock' }
Container running for ft-mint
TypeError: Cannot read property 'id' of undefined
at id (/home/rasholo/nightfall/zkp/code/index.js:139:68)
at process._tickCallback (internal/process/next_tick.js:68:7)
******************************************************************************************************************
Trusted setup has failed for ft-mint.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
Found existing files: [ 'aux-adder.code',
'aux-adder.pcode',
'ft-transfer.code',
'ft-transfer.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/ft-transfer
If you continue, these files will be deleted (except for the '.pcode' file and any '.code' dependencies).
? Continue with the trusted setup? y/n y
deleting ft-transfer.code
Files remaining: [ 'aux-adder.code', 'aux-adder.pcode', 'ft-transfer.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/ft-transfer
Filing checks for codeFile: ft-transfer.pcode
/home/rasholo/nightfall/zkp/code/gm17/ft-transfer/ft-transfer.pcode was copied to safe-dump/ft-transfer.pcode
Checking for 'import' files in the .code file ft-transfer
codeFileName: ft-transfer
codeFile: ft-transfer.code
outputDirPath: /home/rasholo/nightfall/zkp/code/gm17/ft-transfer/
backend: gm17
a: null
ZoKrates running with Nodejs environment setup
Running the container; mounted: /home/rasholo/nightfall/zkp/code/gm17/ft-transfer/:/home/zokrates/code/:cached
{ Error: connect EACCES /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
errno: 'EACCES',
code: 'EACCES',
syscall: 'connect',
address: '/var/run/docker.sock' }
Container running for ft-transfer
TypeError: Cannot read property 'id' of undefined
at id (/home/rasholo/nightfall/zkp/code/index.js:139:68)
at process._tickCallback (internal/process/next_tick.js:68:7)
******************************************************************************************************************
Trusted setup has failed for ft-transfer.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
Found existing files: [ 'nft-burn.code', 'nft-burn.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/nft-burn
If you continue, these files will be deleted (except for the '.pcode' file and any '.code' dependencies).
? Continue with the trusted setup? y/n y
Files remaining: [ 'nft-burn.code', 'nft-burn.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/nft-burn
Filing checks for codeFile: nft-burn.pcode
/home/rasholo/nightfall/zkp/code/gm17/nft-burn/nft-burn.pcode was copied to safe-dump/nft-burn.pcode
Checking for 'import' files in the .code file nft-burn
codeFileName: nft-burn
codeFile: nft-burn.code
outputDirPath: /home/rasholo/nightfall/zkp/code/gm17/nft-burn/
backend: gm17
a: null
ZoKrates running with Nodejs environment setup
Running the container; mounted: /home/rasholo/nightfall/zkp/code/gm17/nft-burn/:/home/zokrates/code/:cached
{ Error: connect EACCES /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
errno: 'EACCES',
code: 'EACCES',
syscall: 'connect',
address: '/var/run/docker.sock' }
Container running for nft-burn
TypeError: Cannot read property 'id' of undefined
at id (/home/rasholo/nightfall/zkp/code/index.js:139:68)
at process._tickCallback (internal/process/next_tick.js:68:7)
******************************************************************************************************************
Trusted setup has failed for nft-burn.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
Found existing files: [ 'nft-mint.code', 'nft-mint.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/nft-mint
If you continue, these files will be deleted (except for the '.pcode' file and any '.code' dependencies).
? Continue with the trusted setup? y/n y
Files remaining: [ 'nft-mint.code', 'nft-mint.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/nft-mint
Filing checks for codeFile: nft-mint.pcode
/home/rasholo/nightfall/zkp/code/gm17/nft-mint/nft-mint.pcode was copied to safe-dump/nft-mint.pcode
Checking for 'import' files in the .code file nft-mint
codeFileName: nft-mint
codeFile: nft-mint.code
outputDirPath: /home/rasholo/nightfall/zkp/code/gm17/nft-mint/
backend: gm17
a: null
ZoKrates running with Nodejs environment setup
Running the container; mounted: /home/rasholo/nightfall/zkp/code/gm17/nft-mint/:/home/zokrates/code/:cached
{ Error: connect EACCES /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
errno: 'EACCES',
code: 'EACCES',
syscall: 'connect',
address: '/var/run/docker.sock' }
Container running for nft-mint
TypeError: Cannot read property 'id' of undefined
at id (/home/rasholo/nightfall/zkp/code/index.js:139:68)
at process._tickCallback (internal/process/next_tick.js:68:7)
******************************************************************************************************************
Trusted setup has failed for nft-mint.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
Found existing files: [ 'nft-transfer.code', 'nft-transfer.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/nft-transfer
If you continue, these files will be deleted (except for the '.pcode' file and any '.code' dependencies).
? Continue with the trusted setup? y/n y
Files remaining: [ 'nft-transfer.code', 'nft-transfer.pcode' ] in /home/rasholo/nightfall/zkp/code/gm17/nft-transfer
Filing checks for codeFile: nft-transfer.pcode
/home/rasholo/nightfall/zkp/code/gm17/nft-transfer/nft-transfer.pcode was copied to safe-dump/nft-transfer.pcode
Checking for 'import' files in the .code file nft-transfer
codeFileName: nft-transfer
codeFile: nft-transfer.code
outputDirPath: /home/rasholo/nightfall/zkp/code/gm17/nft-transfer/
backend: gm17
a: null
ZoKrates running with Nodejs environment setup
Running the container; mounted: /home/rasholo/nightfall/zkp/code/gm17/nft-transfer/:/home/zokrates/code/:cached
{ Error: connect EACCES /var/run/docker.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
errno: 'EACCES',
code: 'EACCES',
syscall: 'connect',
address: '/var/run/docker.sock' }
Container running for nft-transfer
TypeError: Cannot read property 'id' of undefined
at id (/home/rasholo/nightfall/zkp/code/index.js:139:68)
at process._tickCallback (internal/process/next_tick.js:68:7)
******************************************************************************************************************
Trusted setup has failed for nft-transfer.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
I've not touched the docker settings so that might be issue
EDIT: It didn't start any docker image, it might be because I didn't give the command sudo permission.
The problem is that I can't execute sudo npm run setup-all as the command won't be recognized
from nightfall.
Solexplorer
commented on July 24, 2024
@Westlad The original issue has been solved using a non-root user, thanks for the input !
Now after running zkp-demo, I get this strange error:
~/nightfall
*** Launching containerized ganache ***
Creating network "nightfall_default" with the default driver
Creating volume "nightfall_mongo-volume" with default driver
Creating volume "nightfall_zkp-code" with local driver
Creating nightfall_ganache_1 ... error
ERROR: for nightfall_ganache_1 Cannot start service ganache: driver failed programming external connectivity on endpoint nightfall_ganache_1 (b225902ded06ea9709b8ac7a5d611c958e6f7015dcdec05dfbd95141ed689592): Error starting userland proxy:
ERROR: for ganache Cannot start service ganache: driver failed programming external connectivity on endpoint nightfall_ganache_1 (b225902ded06ea9709b8ac7a5d611c958e6f7015dcdec05dfbd95141ed689592): Error starting userland proxy:
ERROR: Encountered errors while bringing up the project.
How is that possible ? Do I have to install ganache ?
from nightfall.
mkinney
commented on July 24, 2024
I think the problem is with the http-proxy. The containers were built. They just cannot talk with each other.
I get an error when I try to docker-proxy start:
docker-proxy start
Starting container...
docker: Error response from daemon: driver failed programming external connectivity on endpoint http-proxy (b90148fe49a97d2a04b536baf2cdec039065ce4f172a655f4811bc4da3ecb4c2): Error starting userland proxy:.
root@ubuntu-s-8vcpu-32gb-sfo2-01:~# docker-proxy status
Were you able to get that part working?
from nightfall.
mkinney
commented on July 24, 2024
This is what it should look like (from mac):
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker-proxy start
Starting container...
$ docker-proxy status
Docker: running
Image: downloaded
Container: running
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f75eaeb89c8b codekitchen/dinghy-http-proxy "/app/docker-entrypo…" 8 seconds ago Up 6 seconds 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 19322/tcp, 0.0.0.0:19322->19322/udp http-proxy
Note the ports are mapped.
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney Actually, I get the same error in linux!
I am using Ubuntu maybe it's an issue with distros, who knows.
I've tried using docker-proxy and also trying to use directly dinghy-http-proxy but the same problem occurs.
Don't know if it's a problem related to Docker or to NightFall at this point
from nightfall.
mkinney
commented on July 24, 2024
I might have a solution... add --network host to the docker-proxy script.
# diff docker-proxy docker-proxy.save
142c142
< docker run -d --restart=always -v /var/run/docker.sock:/tmp/docker.sock:ro -v ~/.dinghy/certs:/etc/nginx/certs -p 80:80 -p 443:443 -p 19322:19322/udp -e CONTAINER_NAME=http-proxy --name http-proxy --network host codekitchen/dinghy-http-proxy 1> /dev/null
---
> docker run -d --restart=always -v /var/run/docker.sock:/tmp/docker.sock:ro -v
~/.dinghy/certs:/etc/nginx/certs -p 80:80 -p 443:443 -p 19322:19322/udp -e CONTAINER_NAME=http-proxy --name http-proxy codekitchen/dinghy-http-proxy 1> /dev/null
You can check that it is working by running:
netstat -tulpn | grep 80
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 4884/nginx: master
from nightfall.
mkinney
commented on July 24, 2024
Note: I also ran these commands but not sure if needed yet. Will test.
ip -6 route add 2001:db8:1::/64 dev docker0
sysctl net.ipv6.conf.default.forwarding=1
Edit: do not need these
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney thanks for the inputs !
now docker-proxy is working fine in port 80 but it seems that I still get the error above regarding nightfall_ganache, weird:
Creating nightfall_ganache_1 ... error
ERROR: for nightfall_ganache_1 Cannot start service ganache: driver failed programming external connectivity on endpoint nightfall_ganache_1 (5298eca2a29ad5bdcb29ab60226a00853c83f255c44f22e09c38bfd3827edd2c): Error starting userland proxy:
ERROR: for ganache Cannot start service ganache: driver failed programming external connectivity on endpoint nightfall_ganache_1 (5298eca2a29ad5bdcb29ab60226a00853c83f255c44f22e09c38bfd3827edd2c): Error starting userland proxy:
ERROR: Encountered errors while bringing up the project.
from nightfall.
mkinney
commented on July 24, 2024
Ok @Solexplorer, I'd remove all of the images, ensure no containers are running. Then start the http-proxy and start over. Be sure to run the rm -rf node_modules just to make sure.
To remove containers: docker ps -a then run docker rm xxx where xxx is the first 3 characters of each container.
To remove images: docker images then run docker rmi xxx where xxx is the first 3 characters of each image.
from nightfall.
Solexplorer
commented on July 24, 2024
Thanks again @mkinney !
Now I have to run npm run setup-all again right ?
from nightfall.
mkinney
commented on July 24, 2024
Yes, I think so.
from nightfall.
mkinney
commented on July 24, 2024
I've got 2 digital ocean droplets that I'm testing the steps on. Will update when done.
from nightfall.
mkinney
commented on July 24, 2024
Created issue on docker-proxy aj-may/docker-proxy#5
from nightfall.
mkinney
commented on July 24, 2024
Looks like there's more to it.
Creating nightfall_ganache_1 ... error
ERROR: for nightfall_ganache_1 Cannot start service ganache: driver failed programming external connectivity on endpoint nightfall_ganache_1 (7f5040132600cd17a2340866c87c274d7aaa3f18658d871b67c906109de74189): Error starting userland proxy:
ERROR: for ganache Cannot start service ganache: driver failed programming external connectivity on endpoint nightfall_ganache_1 (7f5040132600cd17a2340866c87c274d7aaa3f18658d871b67c906109de74189): Error starting userland proxy:
Looking at tail -n 50 /var/log/syslog I see:
Jun 3 20:48:45 ubuntu-s-8vcpu-32gb-sfo2-01 dockerd[3674]: time="2019-06-03T20:48:45.262778072Z" level=warning msg="Failed to allocate and map port 8545-8545: Error starting userland proxy: "
from nightfall.
aj-may
commented on July 24, 2024
Looks like you already have something listening on the RPC port. Check to see what might be listening and kill it, or change the docker-compose.yml file to mount ganache to another port
https://docs.docker.com/compose/compose-file/ <- See Ports
from nightfall.
mkinney
commented on July 24, 2024
Thanks, but I don't see anything on that port. netstat -antd | grep 8545 returns nothing.
from nightfall.
aj-may
commented on July 24, 2024
Just to make sure, lets try mapping a different port in docker-compose.yml
ie.
ports:
- 8547:8545
from nightfall.
mkinney
commented on July 24, 2024
Ok. I tried dropping the initial port, but it gave me lines like this:
Jun 3 21:11:15 ubuntu-s-8vcpu-32gb-sfo2-01 dockerd[26331]: time="2019-06-03T21:11:15.279616483Z" level=warning msg="Failed to allocate and map port: Error starting userland proxy: , retry: 9" Jun 3 21:11:15 ubuntu-s-8vcpu-32gb-sfo2-01 dockerd[26331]: time="2019-06-03T21:11:15.304302568Z" level=warning msg="Failed to allocate and map port: Error starting userland proxy: , retry: 10"
from nightfall.
mkinney
commented on July 24, 2024
Tried that, but got same single line error.
I was trying this: systemd/systemd#3374 (comment)
from nightfall.
mkinney
commented on July 24, 2024
I've created /etc/udev/rules.d/01-net-setup-link.rules and /etc/systemd/network/99-default.link but still getting error. Since I changed the ports line to:
ports:
- 8547:8545
I now get these errors:
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.397342] IPv6: ADDRCONF(NETDEV_UP): br-5c1593206a60: link is not ready
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 systemd-timesyncd[598]: Network configuration changed, trying to establish connection.
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 networkd-dispatcher[952]: WARNING:Unknown index 5 seen, reloading interface list
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.611057] br-5c1593206a60: port 1(vethc1c777e) entered blocking state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.611066] br-5c1593206a60: port 1(vethc1c777e) entered disabled state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.611213] device vethc1c777e entered promiscuous mode
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.611775] IPv6: ADDRCONF(NETDEV_UP): vethc1c777e: link is not ready
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.611790] br-5c1593206a60: port 1(vethc1c777e) entered blocking state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.611792] br-5c1593206a60: port 1(vethc1c777e) entered forwarding state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.612179] br-5c1593206a60: port 1(vethc1c777e) entered disabled state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 networkd-dispatcher[952]: WARNING:Unknown index 7 seen, reloading interface list
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 dockerd[1066]: time="2019-06-03T21:25:52.651248684Z" level=warning msg="Failed to allocate and map port 8547-8547: Error starting userland proxy: "
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.649688] br-5c1593206a60: port 1(vethc1c777e) entered disabled state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.651973] device vethc1c777e left promiscuous mode
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 kernel: [ 78.651976] br-5c1593206a60: port 1(vethc1c777e) entered disabled state
Jun 3 21:25:52 ubuntu-s-8vcpu-32gb-sfo2-01 dockerd[1066]: time="2019-06-03T21:25:52.730807928Z" level=error msg="6451a3b577abba05cd06e630b6615aa0ba163e8fc90d9fb1e9ca1a4c7d5e9071 cleanup: failed to delete container from containerd: no such container"
from nightfall.
mkinney
commented on July 24, 2024
@Solexplorer Can I interest you in a mac? (lols)
I'm kinda stumped here. Will keep trying different things, but not really sure how to work-around it.
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney I don't have a Mac unfortunately, it seems that it works mainly on a mac given people that I have contacted.
Will try to find a way to solve it too
from nightfall.
aj-may
commented on July 24, 2024
I don't use Ubuntu super often, but I've gotten bitten by AppArmor before. I don't remember if that controls ports or not.
from nightfall.
mkinney
commented on July 24, 2024
Sorry, but I could not get it to compile on Centos7; I think it is ram/swap related. Tried larger and larger instances. Tried changing swapiness.
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney How much memory did you try with your instances ?
I am using a 32GB instance and I didn't change any settings about the swap .
Don't know if it's relevant now to switch to a greater instance
from nightfall.
Solexplorer
commented on July 24, 2024
@Westlad I am going to try dory today .
@mkinney Did it work for you at the end ?
from nightfall.
mkinney
commented on July 24, 2024
@Solexplorer Sorry. Did not make any progress. Let me know if you have a branch with dory. (or some other http proxy)
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney Actually, I think that neither dory will work, apparently I am getting this error which is similar to the one that I solved with you adding --network host
docker: Error response from daemon: driver failed programming external connectivity on endpoint dory_dinghy_http_proxy (72696bb8650c73cbe363e6b48c002b5296fe4402326aa5eddda098eebc6ddc1b): Error starting userland proxy:.
Failed to start docker container 'dory_dinghy_http_proxy' . Command 'docker run -d -p 80:80 -p 443:443 -v /var/run/docker.sock:/tmp/docker.sock -e 'CONTAINER_NAME=dory_dinghy_http_proxy' --name 'dory_dinghy_http_proxy' freedomben/dory-http-proxy:2.5.9.1' failed
Error starting nginx proxy
docker: Error response from daemon: driver failed programming external connectivity on endpoint dory_dnsmasq (bba6b7d0d4b78094f952dc1db54811e72307d18130dd242ccb8350bfe7c5a7c7): Error starting userland proxy:.
If someone ever finds a way to start NightFall in any linux distro, please share
from nightfall.
mkinney
commented on July 24, 2024
I've tried lots of combinations of ubuntu 16/ubuntu 18 and docker versions (oldest and newest). I'll keep at it, but it is frustrating. It seems like I'm missing something obvious.
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney Did you try disabling/removing appArmor ?
from nightfall.
mkinney
commented on July 24, 2024
Yes, I had run this:
update-rc.d -f apparmor remove
reboot
apt-get remove apparmor
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney I am watching you, please update if it works
from nightfall.
mkinney
commented on July 24, 2024
I'm trying to build on ubuntu 18 now... hopefully I won't have any swap issues. I'm using 16gb ram/32gb swap.
from nightfall.
mkinney
commented on July 24, 2024
I had to spin several digital ocean instances (and destroy them). I ended up using the doctl to facilitate. I'll clean it up and improve it, but here is a rough draft: (Notes: I replaced my ssh-key XXX with a real key and you have to say "yes" upon first ssh)
doctl compute droplet create three --region sfo2 --image ubuntu-18-04-x64 --size s-6vcpu-16gb --ssh-keys XXX
sleep 120
doctl compute ssh three --ssh-command "fallocate -l 32G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile && sysctl vm.swappiness=10 && echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab"
doctl compute ssh three --ssh-command "apt-get update && apt-get -y upgrade"
doctl compute ssh three --ssh-command "apt -y install apt-transport-https ca-certificates curl software-properties-common"
doctl compute ssh three --ssh-command "curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add -"
doctl compute ssh three --ssh-command 'add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"'
doctl compute ssh three --ssh-command "apt -y update && apt-cache policy docker-ce && apt -y install docker-ce"
doctl compute ssh three --ssh-command "cd /usr/local/bin && curl -sL https://raw.githubusercontent.com/aj-may/docker-proxy/master/install.sh | bash; mv /usr/local/bin/docker-proxy /usr/local/bin/docker-proxy2"
doctl compute ssh three --ssh-command "docker-proxy2 start"
doctl compute ssh three --ssh-command "curl -L https://github.com/docker/compose/releases/download/1.25.0-rc1/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose && chmod +x /usr/local/bin/docker-compose"
doctl compute ssh three --ssh-command "curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -"
doctl compute ssh three --ssh-command "apt-get install -y gcc g++ make && apt-get install -y nodejs"
Ninja edit out the git clone step as it should be done as a non-root user.
from nightfall.
mkinney
commented on July 24, 2024
Darn. Didn't compile with 16gb and 32gb swap.
from nightfall.
mkinney
commented on July 24, 2024
I'm getting the
ft-mint SETUP MESSAGE: EXPORT-VERIFIER COMPLETE
�cp: cannot create regular file '/home/zokrates/code/out': Permission denied
cp: cannot create regular file '/home/zokrates/code/out.code': Permission denied
cp: cannot create regular file '/home/zokrates/code/proving.key': Permission denied
cp: cannot create regular file '/home/zokrates/code/verification.key': Permission denied
cp: cannot create regular file '/home/zokrates/code/variables.inf': Permission denied
cp: cannot create regular file '/home/zokrates/code/verifier.sol': Permission denied
error that I'm attributing to memory/swap.
I'm running the compilation under root. I'll switch to a user and try that.
from nightfall.
mkinney
commented on July 24, 2024
So, need these steps:
# create a nightfall user "nf"
useradd -m nf
passwd nf
usermod -aG docker nf
su - nf
bash
git clone https://github.com/EYBlockchain/nightfall.git
cd nightfall
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney Yes, exactly, that's what worked for me although I made a user with sudo authorization
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney Did you delete the droplet that compiled successfully for you?
from nightfall.
mkinney
commented on July 24, 2024
I'm still compiling under non-root.
from nightfall.
Solexplorer
commented on July 24, 2024
There's another problem, the ./zkp-demo compiles successfully but I am not able to see the Angular UI.
nightfall.docker doesn't return anything even localhost:80 returns just the welcome page of dinghy-http-proxy
from nightfall.
mkinney
commented on July 24, 2024
I was going to try this when I start up the ./zpk-demo step:
ssh -L8000:localhost:80 root@IP
Did you get anything in the /etc/resolver/docker file?
root@three:~# cat /etc/resolver/docker
# Generated by docker-proxy
nameserver 127.0.0.1
port 19322
What does docker ps -a | grep http show for you?
root@three:~# docker ps -a | grep http
e90fc440790c codekitchen/dinghy-http-proxy "/app/docker-entrypo…" 15 minutes ago Up 15 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 19322/tcp, 0.0.0.0:19322->19322/udp http-proxy
from nightfall.
Solexplorer
commented on July 24, 2024
cat /etc/resolver/docker returns me:
nameserver 127.0.0.1
port 19322
docker ps -a | grep http returns:
8200397c4a25 codekitchen/dinghy-http-proxy "/app/docker-entrypo…" About an hour ago Up About an hour 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 19322/tcp, 0.0.0.0:19322->19322/udp http-proxy
from nightfall.
mkinney
commented on July 24, 2024
Are you running this ubuntu from a desktop machine or a remote instance like a Digital Ocean droplet?
from nightfall.
Solexplorer
commented on July 24, 2024
I am running this from a remote instance, connecting with vnc in order to look at the UI
from nightfall.
mkinney
commented on July 24, 2024
Ah. So, vnc should have local browsing working... huh.
It's still compiling, but I was going to try to forward the port and use my local browser. I was going to start a new ssh session like this:
ssh -L8000:localhost:80 root@IP
Then in my mac open up http://localhost:8000 (but I've not yet tested that it will work)
from nightfall.
Solexplorer
commented on July 24, 2024
Actually I've tried forwarding the port as you have suggested but I see this page
from nightfall.
Solexplorer
commented on July 24, 2024
And I see that the demo has compiled correctly:
zkp_1 | VK setup complete
ui_1 |
ui_1 | Date: 2019-06-06T20:54:28.741Z
ui_1 | Hash: cd9cee5ec28e8668ca0b
ui_1 | Time: 16909ms
ui_1 | chunk {main} main.js, main.js.map (main) 357 kB [initial] [rendered]
ui_1 | chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 236 kB [initial] [rendered]
ui_1 | chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered]
ui_1 | chunk {scripts} scripts.js, scripts.js.map (scripts) 492 kB [entry] [rendered]
ui_1 | chunk {styles} styles.js, styles.js.map (styles) 1.32 MB [initial] [rendered]
ui_1 | chunk {vendor} vendor.js, vendor.js.map (vendor) 6.68 MB [initial] [rendered]
ui_1 | ℹ ｢wdm｣: Compiled successfully.
from nightfall.
Solexplorer
commented on July 24, 2024
I will try it tomorrow as it's too late right now but I will let you know if I find a way to solve the issue
from nightfall.
mkinney
commented on July 24, 2024
I was able to get the GUI, but I bypassed the docker-proxy2 stuffs:
docker inspect nightfall_ui_1 | grep IPAddress
root@three:~# docker inspect nightfall_ui_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.18.0.6",
root@three:~#
ssh -L 8000:172.18.0.6:80 root@IP_OF_DO
http://localhost:8000/login gives me a login to Nightfall
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney hiya! It works now
Issue solved and Issue closed !
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney Does it create the account to you ?
from nightfall.
mkinney
commented on July 24, 2024
Crap. No.
from nightfall.
mkinney
commented on July 24, 2024
I've been trying lots of things. This is a good test case to validate that the internal dns is working as expected:
docker run -d -p 8000:8000 --hostname hello.docker alpine ash -c "while true; do echo hello world; sleep 1; done"
docker run -d -p 8001:8001 --hostname hello2.docker alpine ash -c "while true; do echo hello world; sleep 1; done"
root@three:/home/nf/nightfall# docker run -d -p 8000:8000 --hostname hello.docker alpine ash -c "while true; do echo hello world; sleep 1; done"
d10c5344b59946388923abd90da61b016f6c5cf45b61d1b0fe7d2a314d8e1ee5
root@three:/home/nf/nightfall# docker run -d -p 8001:8001 --hostname hello2.docker alpine ash -c "while true; do echo hello world; sleep 1; done"
6fe77a2e033e9e5cf249a131d1c96923808dff337a874f8bd4a3b472eb28e8c2
root@three:/home/nf/nightfall# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6fe77a2e033e alpine "ash -c 'while true;…" 3 seconds ago Up 2 seconds 0.0.0.0:8001->8001/tcp inspiring_turing
d10c5344b599 alpine "ash -c 'while true;…" 6 seconds ago Up 5 seconds 0.0.0.0:8000->8000/tcp sharp_neumann
root@three:/home/nf/nightfall# docker exec -it inspiring_turing ash
/ # hostname
hello2.docker
/ # ping hello.docker
ping: bad address 'hello.docker'
If we can get those docker containers to resolve to each other then we're golden.
I've tried several things:
rm -f /etc/resolv.conf
ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
reboot
vi /etc/systemd/resolved.conf
service systemd-resolved restart
systemd-resolve --status
And:
cat /etc/docker/daemon.json
{
"dns": ["127.0.0.11", "8.8.8.8"],
"dns-search": ["docker"],
"dns-opts":["use-vc"]
}
then systemctl restart docker
but, I cannot seem to get that test case above to work. I'll keep at it later... but sharing what I've tried.
from nightfall.
mkinney
commented on July 24, 2024
Doing research.
On centos7, selinux disabled, no dnsmasq, no entries in /etc/resolv.conf, with the ip address of docker0:
# cat /etc/docker/daemon.json
{
"dns": [
"172.17.0.1"
]
}
[root@centos ~]# ifconfig docker0 | grep "inet "
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
These are results:
docker network create --driver bridge alpine-net
docker run -d -p 8000:8000 --hostname hello.docker --name hello.docker --network alpine-net alpine ash -c "while true; do echo hello world; sleep 1; done"
docker run -d -p 8001:8001 --hostname hello2.docker --name hello2.docker --network alpine-net alpine ash -c "while true; do echo hello world; sleep 1; done"
# when done
docker network rm alpine-net
Here's the results:
[root@centos ~]# docker network create --driver bridge alpine-net
58253e624bbfc86cd0df88ecb839e29ba4c181543efa84216631009425952641
[root@centos ~]# docker run -d -p 8000:8000 --hostname hello.docker --name hello.docker --network alpine-net alpine ash -c "while true; do echo hello world; sleep 1; done"
9f5accc527139f26c57981f6331a2b181494e4b24eb54ae1023b057d40c168ab
[root@centos ~]# docker run -d -p 8001:8001 --hostname hello2.docker --name hello2.docker --network alpine-net alpine ash -c "while true; do echo hello world; sleep 1; done"
8a682bba888faf45f9973250946c9ec999ad49f349054dd66bd387a216ef3a0a
[root@centos ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8a682bba888f alpine "ash -c 'while true;…" 14 seconds ago Up 13 seconds 0.0.0.0:8001->8001/tcp hello2.docker
9f5accc52713 alpine "ash -c 'while true;…" 16 seconds ago Up 14 seconds 0.0.0.0:8000->8000/tcp hello.docker
cdb97e363231 codekitchen/dinghy-http-proxy "/app/docker-entrypo…" About an hour ago Up About an hour 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 19322/tcp, 0.0.0.0:19322->19322/udp http-proxy
[root@centos ~]# docker exec -it hello2.docker ash
/ # ping hello
ping: bad address 'hello'
/ # hostname
hello2.docker
/ # ping hello.docker
PING hello.docker (172.20.0.2): 56 data bytes
64 bytes from 172.20.0.2: seq=0 ttl=64 time=0.202 ms
64 bytes from 172.20.0.2: seq=1 ttl=64 time=0.133 ms
^C
--- hello.docker ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.133/0.167/0.202 ms
/ # ping hello2.docker
PING hello2.docker (172.20.0.3): 56 data bytes
64 bytes from 172.20.0.3: seq=0 ttl=64 time=0.065 ms
^C
--- hello2.docker ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.065/0.065/0.065 ms
/ # [root@centos ~]#
[root@centos ~]# docker kill 8a 9f
do8a
9f
[root@centos ~]# docker rm 8a 9f
8a
9f
[root@centos ~]# docker network rm alpine-net
alpine-net
[root@centos ~]#
A similar docker-compose.yml would look like this:
version: "3"
services:
hello:
image: alpine
hostname: hello
#domainname: docker
command: ash -c "while true; do echo hello world; sleep 1; done"
ports:
- 8000:8000
networks:
- alpine-net
hello2:
image: alpine
hostname: hello2
#domainname: docker
command: ash -c "while true; do echo hello world; sleep 1; done"
ports:
- 8001:8001
networks:
- alpine-net
networks:
alpine-net:
driver: bridge
Here's what it looks like when you run docker-compose up and then go to another window:
[root@centos ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d801a80d3e29 alpine "ash -c 'while true;…" 18 seconds ago Up 17 seconds 0.0.0.0:8000->8000/tcp root_hello_1
61cd83936245 alpine "ash -c 'while true;…" 18 seconds ago Up 17 seconds 0.0.0.0:8001->8001/tcp root_hello2_1
cdb97e363231 codekitchen/dinghy-http-proxy "/app/docker-entrypo…" About an hour ago Up About an hour 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 19322/tcp, 0.0.0.0:19322->19322/udp http-proxy
[root@centos ~]# docker exec -it root_hello_1 ash
/ # ping hello1
ping: bad address 'hello1'
/ # ping hello2
PING hello2 (172.19.0.2): 56 data bytes
64 bytes from 172.19.0.2: seq=0 ttl=64 time=0.163 ms
64 bytes from 172.19.0.2: seq=1 ttl=64 time=0.099 ms
^C
--- hello2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.099/0.131/0.163 ms
/ # hostname
hello
Notes:
- Cannot use the
domainnameoption and ping host.domain for some reason. - Cannot resolve container names in host. :-(
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney I will try today messing around and try to find a solution but I don't assure that I will be able to solve it.
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney I was not able to find a solution to that problem...
@aj-may @Westlad Can you try to run NightFall on any linux distro and tell us if it works for you ?
from nightfall.
mkinney
commented on July 24, 2024
I suspect that if the container names were single hostnames that it would work, but I've not tested it. For example, "accounts.nightfall.docker" would just be "accounts". (at least based on what on my tests above)
from nightfall.
Solexplorer
commented on July 24, 2024
@mkinney I've tried it, but unfortunately it didn't work.
Can't I run NightFall from the CLI ?
from nightfall.
brian-lc
commented on July 24, 2024
Hi, I'm also having the problem described in this issue. However, I don't think the solution that worked for the OP is going to work for me. If I follow the thread correctly, it seems that the OP solved the problem by running as a non-root user. I'm already running this as non-root user.
My setup:
Mac OX 10.14.5
16GB memory
2.9 GHz Intel Core i7
Docker Desktop 2.0.0.3
Docker settings: memory 12GB, 6 cpus, 4GB swap.
Python 2.7
node 10.15.3
I've gone through the setup twice to make sure I'm not missing something.
The error I'm seeing appears to be the same...
I'm running $ npm run setup-all from the zpk directory. I have run npm ci previously.
Export Verifier nft-transfer ...
Error: panicked at 'couldn't open verification.key: No such file or directory (os error 2)', zokrates_cli/src/bin.rs:477:33
note: Run with `RUST_BACKTRACE=1` for a backtrace.
at IncomingMessage.stream.on (/Users/brian/Projects/nightfall/zkp/src/zokrates.js:37:16)
at IncomingMessage.emit (events.js:194:15)
at endReadableNT (_stream_readable.js:1125:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
undefined
nft-transfer SETUP MESSAGE: EXPORT-VERIFIER COMPLETE
�cp: cannot stat '/home/zokrates/proving.key': No such file or directory
cp: cannot stat '/home/zokrates/verification.key': No such file or directory
Icp: cannot stat '/home/zokrates/verifier.sol': No such file or directory
nft-transfer SETUP MESSAGE: FILES COPIED TO THE MOUNTED DIR WITHIN THE CONTAINER. THE FILES WILL NOW ALSO EXIST WITHIN YOUR LOCALHOST'S FOLDER: /Users/brian/Projects/nightfall/zkp/code/gm17/nft-transfer/
Key extraction nft-transfer ...
{ Error: ENOENT: no such file or directory, open '/Users/brian/Projects/nightfall/zkp/code/gm17/nft-transfer/verifier.sol'
at Object.openSync (fs.js:438:3)
at Object.readFileSync (fs.js:343:35)
at Object.readFileSync (/Users/brian/Projects/nightfall/zkp/code/tools-key-extractor.js:18:6)
at keyExtractor (/Users/brian/Projects/nightfall/zkp/code/index.js:249:41)
at process._tickCallback (internal/process/next_tick.js:68:7)
errno: -2,
syscall: 'open',
code: 'ENOENT',
path:
'/Users/brian/Projects/nightfall/zkp/code/gm17/nft-transfer/verifier.sol' }
******************************************************************************************************************
Trusted setup has failed for nft-transfer.code. Please see above for additional information relating to this error.
The most common cause of errors when using this tool is insufficient allocation of resources to Docker.
You can go to Docker's settings and increase the RAM being allocated to Docker. See the README for more details.
******************************************************************************************************************
I'm not quite sure what to try next. Any advice is welcome. I suppose I will explore the possibility of running setup for just the nft-transfer on it's own. Perhaps that will yield some insights (assuming it's possible to do that).
FWIW, nft-mint, nft-burn steps seem to work just fine.
from nightfall.
iAmMichaelConnor
commented on July 24, 2024
@BreakPointer - see here for running trusted setup for a single computation. See also here if you want to have a go at manually doing what the setup scripts do.
from nightfall.
ChaitanyaKonda
commented on July 24, 2024
@Solexplorer @mkinney Thank you for working on this issue with running nightfall on linux. This has been raised in #20 and is currently being worked on by Nightfall team. So closing this issue as this is a duplicate and under a different issue title.
from nightfall.
Related Issues (20)
- Whats more private than a hash wallet address ?? just make a new account and wallet .. this proj is moot
- Issue while account creation after a login failure HOT 1
- Historic Public Key Roots let user avoid blacklisting
- Check that correct admin public keys are being used
- Remove redundant error-checking code
- Check privacy settings of functions and state variables
- small code cleanups
- run transferFTCommitment failed!!! HOT 5
- Cannot successfully run the .nightfall script HOT 2
- OPCoin commitment transfer failing HOT 4
- All inline callback function should be arrow function (airbnb standards)
- do not export directly from an import (airbnb strandards) HOT 1
- Don’t use iterators(for-in or for-of). Prefer JavaScript’s higher-order (airbnb standards)
- empty line before single line comments (airbnb standards)
- filename should exactly match the name of its default export (airbnb standards)
- Do not use JavaScript getters/setters (airbnb standards)
- Error while minting commitment token HOT 1
- Refactor nightfall/nightlite responsibilities
- errors while running transactions HOT 6
- Not able to make Nighfall usage non interactive
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nightfall.