Closed freidenker closed 1 year ago
I can't reproduce it on my machine.
You may check the graftcp-local log, or check the proxy server is working.
I can't reproduce it on my machine.
You may check the graftcp-local log, or check the proxy server is working.
not sure if it was related with the GFW. i have installed a squid http proxy server in aws us-west-2 region, then used graftcp in shanghai local machine to pull gcr images. Also failed pulling gcr images with ss proxy. have any suggestions?
You may check the proxy server is working: curl -x http://my_proxy:3128 http://www.google.com/
.
You may check the proxy server is working:
curl -x http://my_proxy:3128 http://www.google.com/
.
hi, looks like find the root cause, actullay i run graftcp-local service in a docker container, in a gitlab runner with a docker container. meanwile the ss5 server didn't get the requests log. but mgraftcp is ok. so another question: does graftcp-local work in container?
You may check the proxy server is working:
curl -x http://my_proxy:3128 http://www.google.com/
.hi, looks like find the root cause, actullay i run graftcp-local service in a docker container, in a gitlab runner with a docker container. meanwile the ss5 server didn't get the requests log. but mgraftcp is ok. so another question: does graftcp-local work in container?
Are graftcp and graftcp-local in the same container? They communicate using named pipes, and graftcp-local needs to access /proc to determine information related to graftcp. They need to be in the same environment to work properly.
You may check the proxy server is working:
curl -x http://my_proxy:3128 http://www.google.com/
.hi, looks like find the root cause, actullay i run graftcp-local service in a docker container, in a gitlab runner with a docker container. meanwile the ss5 server didn't get the requests log. but mgraftcp is ok. so another question: does graftcp-local work in container?
Are graftcp and graftcp-local in the same container? They communicate using named pipes, and graftcp-local needs to access /proc to determine information related to graftcp. They need to be in the same environment to work properly.
yes, they were in same container.
-config
does not work, it always use default configuration in /etc/graftcp-local/graftcp-local.conf
.--blackip-file
to ignore them. like 10.16.0.2 127.0.0.53
and graftcp bash still not work in docker container
graftcp-local service issue got fixed, the parameter
-config
does not work, it always use default configuration in/etc/graftcp-local/graftcp-local.conf
.
- on ubuntu system systemd-resolved service listen tcp 127.0.0.53:53 port to resolve dns, and aws ec2 also have a internal dns service, i added these 2 IPs into graftcp parameter
--blackip-file
to ignore them. like10.16.0.2 127.0.0.53
and graftcp bash still not work in docker container
Please check if your docker supports ptrace
.
graftcp-local service issue got fixed, the parameter
-config
does not work, it always use default configuration in/etc/graftcp-local/graftcp-local.conf
.
- on ubuntu system systemd-resolved service listen tcp 127.0.0.53:53 port to resolve dns, and aws ec2 also have a internal dns service, i added these 2 IPs into graftcp parameter
--blackip-file
to ignore them. like10.16.0.2 127.0.0.53
- How do you start graftcp-local service? If it run as a service, please check the it's systemd-unit service conf.
- This tool does not have the ability to affect the dns.
graftcp-local service issue got fixed, the parameter
-config
does not work, it always use default configuration in/etc/graftcp-local/graftcp-local.conf
.
- on ubuntu system systemd-resolved service listen tcp 127.0.0.53:53 port to resolve dns, and aws ec2 also have a internal dns service, i added these 2 IPs into graftcp parameter
--blackip-file
to ignore them. like10.16.0.2 127.0.0.53
- How do you start graftcp-local service? If it run as a service, please check the it's systemd-unit service conf.
- This tool does not have the ability to affect the dns.
graftcp-local -service install & graftcp-local -service start.
right, systemd-unit service conf is always /etc/graftcp-local/graftcp-local.conf
.
and graftcp bash still not work in docker container
Please check if your docker supports
ptrace
.
for GitLab CICD pipeline, we can define that image's Dockerfile to implement graftcp bash
.
ENTRYPOINT ["/bin/bash", "-c", "graftcp-local -service start; /opt/graftcp-blackip.sh; graftcp --blackip-file=/opt/blackips bash"]
just changed the issues title, to the users of graftcp with similar issues.
thanks @hmgle for your help. the --blackip-file looks does not support CIDR, right?
thanks @hmgle for your help. the --blackip-file looks does not support CIDR, right?
Not supported.
my proxy server is a squid proxy server.
failed at
graftcp crane pull gcr.io/kaniko-project/executor:v1.9.0-debug kaniko.tar -v
only failed on pulling gcr.io images, works on other registriesroot@18f481e9c3e5:/opt#
crane version
0.14.0 https://github.com/google/go-containerregistry root@18f481e9c3e5:/opt#graftcp --version
graftcp v0.4root@18f481e9c3e5:/opt#
cat /etc/graftcp-local/graftcp-local.conf
the error log: root@18f481e9c3e5:/opt#
graftcp crane pull gcr.io/kaniko-project/executor:v1.9.0-debug kaniko.tar -v