Thank you so much for your reply and the pull request. I destroyed the previous instance, re-created another (same OS as previous), cloned Forem from the original repository and I am still getting errors:
This is the first error that shows up when using Podman to build and run the container.
STEP 19: COPY ./.ruby-version "${APP_HOME}"
--> d6bfc3e5cf4
ERRO[0527] error deleting build container "c90f7f38204a048368598dcdc8693a69f046691da09deab50b96c4bc485a7771": identifier is not a container
Error: identifier is not a container: error preparing container for next step: error creating build container: error creating container: error creating read-write layer with ID "ea41b3fecfebbf4001c2273fe73d831cff068055c5f6886e45d752e23ad41c5f": no space left on device
125
Starting the Forem container stack...
using podman version: podman version 2.0.4
Error: error inspecting object: unable to find a name and tag match for forem-rails in repotags: no such image
podman build -t forem-rails:latest -f ./Dockerfile .
Installing Forem using Docker also has few errors that I would like to mention:
I was not able to run "bin/container-setup" directly without sudo, so I added my current user to docker group with the following command:
$ bin/container-setup
Building the Forem container image!
This will take a while if you are building the container for the first time.
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
$ sudo setfacl -m user:$USER:rw /var/run/docker.sock
$ bin/container-setup
At "Step 9" it has the same issue as podman-compose.
Step 9/30 : RUN groupadd -g "${APP_GID}" "${APP_USER}" && adduser -u "${APP_UID}" -g "${APP_GID}" -d "${APP_HOME}" "${APP_USER}"
---> Running in 3c1f8cb19915
adduser: warning: the home directory /opt/apps/forem/ already exists.
adduser: Not copying any file from skel directory into it.
There are multiple warnings when linking dependencies:
Correct me if I am wrong but the pull request is already merged into the master repository, right? If so, I cloned the repository again and tried to run the "container-setup" again.
I was able to run it on Docker with no issue, though.
Error: identifier is not a container: error preparing container for next step: error creating build container: error creating container: error creating read-write layer with ID "ea41b3fecfebbf4001c2273fe73d831cff068055c5f6886e45d752e23ad41c5f": no space left on device
This might be due to disk space issues on your computer? Try nuking the podman volumes:
What is the minimum requirement for disk space? I had allocated 30 GB of space for this.
I was able to install Forem by manually installing everything but I had few problems such as:
Moving from development environment to production. Since this is literally my first time working with Ruby on Rails.
Changing port from 3000 to 80. I figured Procfile.dev was responsible for server port but I had issue with permission:
Errno::EACCES in at_exit
Permission denied - bind(2) for "0.0.0.0" port 80
So a quick workaround was to port forward from 80 to 3000 but I don't think this is the correct way.
Is there any documentation or guide which could help me with these issues? I think if someone was able to provide a guide on how to fully install Forem from basic configurations to making it production-ready, that would be great!
I allocate 50GB in my test environments which should be fine. If you are running Forem as a non root user (which is recommended) you will want to do this:
sudo sh -c "echo 0 > /proc/sys/net/ipv4/ip_unprivileged_port_start"
which will let a non root user bind to lower ports like port 80.
Please check out this PR which should fix the issues you are seeing.
github.com/forem/forem/pull/9835
Thank you so much for your reply and the pull request. I destroyed the previous instance, re-created another (same OS as previous), cloned Forem from the original repository and I am still getting errors:
Installing Forem using Docker also has few errors that I would like to mention:
Edit: Ah, nevermind. It took some time but Docker seems to be working fine.
Did you check out my PR's branch and use that with Podman?
Correct me if I am wrong but the pull request is already merged into the master repository, right? If so, I cloned the repository again and tried to run the "container-setup" again.
I was able to run it on Docker with no issue, though.
~No it's in a branch off the main repo. You need to check it out first and test it out.~
Strike this. It was merged and I missed it. It should work. I tested it on my end with Podman before pushing it up.
This error
This might be due to disk space issues on your computer? Try nuking the podman volumes:
podman volume listpodman volume prumeWhat is the minimum requirement for disk space? I had allocated 30 GB of space for this.
I was able to install Forem by manually installing everything but I had few problems such as:
Moving from development environment to production. Since this is literally my first time working with Ruby on Rails.
Changing port from 3000 to 80. I figured Procfile.dev was responsible for server port but I had issue with permission:
So a quick workaround was to port forward from 80 to 3000 but I don't think this is the correct way.
Is there any documentation or guide which could help me with these issues? I think if someone was able to provide a guide on how to fully install Forem from basic configurations to making it production-ready, that would be great!
I allocate 50GB in my test environments which should be fine. If you are running Forem as a non root user (which is recommended) you will want to do this:
sudo sh -c "echo 0 > /proc/sys/net/ipv4/ip_unprivileged_port_start"which will let a non root user bind to lower ports like port 80.
Great, thank you! :)