-
Notifications
You must be signed in to change notification settings - Fork 31
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.
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
Container fails to start #118
Comments
Could you please provide more information about what are you trying to do? |
Im just trying to run the container with your docker-compose. It just loops. Is the image exsposed to be only 22MB |
I run 100 containers in my environment so i would like to think there is nothing wrong with my config. Im going to try version 1.7 and see if that makes a difference |
I'm running latest amd64, docker reports it's 20.9MB, works for me. You will have to share some more detailed info. Does pacoloco have log levels? Check dockerd logs. Volume mounts writeable? Address pool or something used up? |
I will check again this evening and try to log what happens if i use docker events i can see container being created and destroyed almost instantly. Is there a specific user this container runs as? since i use nfs volumes i want to make sure permissions are right. |
@awptechnologies start with the docker-related documentation https://github.com/anatol/pacoloco?tab=readme-ov-file#docker If it does not work for you then report your config, steps that you made and logs. |
Whatever issue was commenting out the archlinux-reflector line allowed it to start. Any reason why? |
Example For the Anyway, when I started the
|
Thats exactly what i got. I then got an error that said path /var/cache/pacoloco/pkgs/archlinux didn't exist so i created it manually and then the error was no longer there. But when i set up the server in my arch host it failed to get updates. do i have to let pacoloco pull packages during its cron job first? |
error: failed retrieving file 'core.db' from 10.1.1.24:9129 : Failed to connect to 10.1.1.24 port 9129 after 2 ms: Could not connect to server |
fixed it in the pacoloco.yaml i had to change the server address to 0.0.0.0. Totally slipped my mind i forgot that 127.0.0.1 only listens from localhost not from any host. |
@anatol perhaps the README should be changed to refer to pacoloco.yaml.sample rather than maintaining a copy with example values that are in some cases misleading? And a note could be added in either place about using 0.0.0.0 with docker/container-based setup. |
@HarHarLinks I agree that make sense to make README more usable and closer to what users need at at the real systems. Would you be able send a quick PR for it? |
after multiple attempts the container will not start. keeps getting non 0 exit code.
The text was updated successfully, but these errors were encountered: