PhaseI never had this issue to create the DOCKER chain...
PhaseCan you do it by hand? With root user? The command line it gives looks valid. I would try a:
sudo iptables -t nat -N DOCKER
i create a dockerfile based of node
FROM node:12.18.1 RUN mkdir /usr/local/src/app \ && mkdir /usr/local/src/app/node_modules \ && chown node /usr/local/src/app \ && chown node /usr/local/src/app/node_modules WORKDIR /usr/local/src/app COPY app-scripts /usr/local/src/app-scripts COPY package.json . COPY package-lock.json . RUN npm -v CMD [ "node" ]
I wanted to leave it installable in a docker-composes file with the following execution
api: image: my-image-node:0.0.1 build: context: . dockerfile: Dockerfile.dev command: npm install && npm run start:dev environment: NODE_ENV: development BUILD_ENV: development
when i launch the server i got this error
id: 'npm': no such user
is there someone who can help me? Thanks
--network hostapparently isn't supported on my development OS (mac)
HaleyHow can I define the location on the host. I want it to go to /var/nfs/phobos-static and /var/nfs/phobos-files
Haleyany idea? (this is, using a docker-compose file).
Meliodas* hello everyone,
- ./config-data:/var/config-data environment: - JAVA_OPTS= -DEUREKA_SERVER=http://registry:8761/eureka -Dspring.cloud.config.server.native.searchLocations=/var/config-data depends_on: - registry ports: - "8888:8888"
I am trying to fix this from the last 3 days and not able to fix
Command------ docker run -ti -p 127.0.0.1:5432:5432 -e POSTGRES_HOST_AUTH_METHOD=trust -e LC_COLLATE=en_US.UTF8 -e LC_CTYPE=en_US.UTF8 --rm postgres:11 -c log_statement=all
Error------ docker: Error response from daemon: driver failed programming external connectivity on endpoint trusting_feistel (c76e7077bd6e012a2282670506334a0aef50695489dc20a1992e00e205f0954c): Error starting userland proxy: listen tcp 127.0.0.1:5432: bind: address already in use.
I'm trying to run Docker inside Docker and mounting the
/var/run/docker.sock socket. The socket gets the following permissions and ownership inside the container:
srwxr-xr-x 1 root root 0 Nov 8 17:20 /var/run/docker.sock
meaning it can't be accessed from inside the container with regular user privileges.
What's the best way to resolve this?