8000 Error running locally · Issue #23 · odoocker/odoocker · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Error running locally #23

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.

Sign up for GitHub

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

Jump to bottom
Open
nelsonvega opened this issue Jun 28, 2024 · 10 comments
Open

Error running locally #23

nelsonvega opened this issue Jun 28, 2024 · 10 comments
Assignees
@yhaelopez

Comments

@nelsonvega
Copy link

image
@bosd
Copy link
bosd commented Jun 28, 2024

Can you provide a little bit more information?

@nelsonvega
Copy link
Author
nelsonvega commented Jun 28, 2024 •
edited
Loading

I've just cloned the repo, set the variables in the .env, and did docker-compose up -d
btw, I'm running Windows but getting the same error on Mac

@bosd
Copy link
bosd commented Jun 29, 2024

Oops, can't help you with that.
I don't know if these platforms are supported.
I'm using linux and it's ok.
Maybe you can use a linux VM?

@ppsaheed
Copy link
ppsaheed commented Jul 3, 2024

The setup works fine on Linux and older Mac systems. However, there are errors on newer Macs because Docker primarily supports AMD64 architecture, while newer Macs use ARM64. I tested it on a Mac with an M1 chip, and it failed.

@bosd
Copy link
bosd commented Jul 3, 2024

However, there are errors on newer Macs because Docker primarily supports AMD64 architecture, while newer Macs use ARM64. I tested it on a Mac with an M1 chip, and it failed.

I had another Odoo Docker framework ( Doodba ) running fine on a arm system.
Had to use another PostgreSQL base version, architecture specific.

Maybe this helps.. resolving the issue here..

@yhaelopez
Copy link
Contributor

@bosd Is there a way we can integrate this option into Odoocker?
If you give me the insights I can do some work around with the Environment Variables (defaulting to Linux, but with documented options for Windows & recent Mac versions)

@yhaelopez
Copy link
Contributor

@nelsonvega Is not clear for me what's actually failing in your build.
Can you share more details, please?

@yhaelopez yhaelopez self-assigned this Jul 16, 2024
@TheLiminalDream
Copy link
TheLiminalDream commented Sep 30, 2024 •
edited
Loading

I have ran into the same issue on windows, and it was due to the formatting of the clone-addons.sh file, the carriage returns were not properly formatted (not sure why)

I went and ran this on the file and was able to get past that error, I have another error now but was able to atleast start the cloning process.

cd C:\path\to\your\clone\odoo
Get-ChildItem -File -Recurse | % { $x = get-content -raw -path $.fullname; $x -replace "rn","`n" | set-content -path $.fullname }

Edit:
The other error was do to a windows carriage return on the last line.

you could also use dos2unix formatter to make life a bit easier as well. I have ran into this countless times when doing cross system automations.

@raininja
Copy link

I have ran into the same issue on windows, and it was due to the formatting of the clone-addons.sh file, the carriage returns were not properly formatted (not sure why)
Edit: The other error was do to a windows carriage return on the last line.

"The main difference between Windows and Linux carriage returns is that Windows uses a carriage return and line feed ("\r\n") to terminate a line, while Linux uses only a line feed ("\n")."

@ubidev
Copy link
ubidev commented Dec 17, 2024 •
edited
Loading

Hi
I had the same problem on my windows machines but even after fixing the cariage returns issue with the following command (the one submitted in a previous post is full of problems)

Get-ChildItem -File -Recurse | % { $x = Get-Content  -Path $_.FullName; $x -Replace "`r`n","`n" | Set-Content -Path $_.FullName }

BUT THEN, the docker compose would tell me clone-addons.sh depends on /bin/bash....

image

So I took the route of WSL2 since docker desktop on windows uses it.

I installed the ubuntu 20.04 LTS WSL image then cloned the repo inside that wsl container and executed commands of the getting started section without issue:

sudo apt update
sudo apt dist-upgrade
sudo apt autoremove
mkdir src
cd src
git clone https://github.com/odoocker/odoocker.git
cd odoocker
cp .env.example .env && cp docker-compose.override.local.yml docker-compose.override.yml
echo '127.0.0.1 erp.odoocker.test' | sudo tee -a /etc/hosts
echo '127.0.0.1 pgadmin.odoocker.test' | sudo tee -a /etc/hosts
docker-compose up -d --build && docker-compose logs odoo

Now the odoocker container is running and showing up in my windows docker console :)

image

Hope this help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yhaelopez yhaelopez

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@raininja @nelsonvega @bosd @ubidev @TheLiminalDream @ppsaheed @yhaelopez
0