Open vbabuEM opened 1 month ago
Here is Benoit from Startin'blox (France). We are diving into Beckn for some projects.
We are in the phase of setting up the Onix Project on EC2 Test instances and we do have the same error, could a patch be released please ?
@balessan I also faced the same issue. And this is how I resolved it.
Not sure why I noticed that when running docker-compose, it was showing segmentation fault.
I tried deleting all docker files using
sudo apt purge docker docker-compose docker-init
This did not work.
I was still able to execute docker commands.
I used the whereis
command to find the where all the docker files are situated and deleted using the rm command
whereis docker
whereis docker-compose
Now deleting it
sudo rm /usr/bin/docker
sudo rm /usr/bin/docker-compose
Like wise, deleted all the docker files manually.
At last for my Debian Machine went to the official docker docs and installed it from there .
https://discord.com/channels/933320455903907840/1247447145137573949/1247447145137573949 Ddhruv I was able to clone the ONIX in an ec2 instance, I have configured a SSL and used the domain provided by EC2, now once I give the domain for registry setup, some issue is coming up as
................Installing Registry service................ unknown shorthand flag: 'f' in -f See 'docker --help'.
Now, this was not expected, but it can be due to different versions of docker, etc. Then finally the Onix shows the registry installation is completed but the server is not started. Error in some docker command Installs but server is not started
Ddhruv OP — Yesterday at 12:59 PM Found the problem, in the installation file, its given as "docker compose -f", where as it should look like "docker-compose -f"