docker run -d \
-p 8081:8081 \
-e ME_CONFIG_MONGODB_ADMINUSERNAME-admin \
-e ME_CONFIG_ MONGODB_ADMINPASSWORD=password \
--net mongo-network \
--name mongo-express \
-e ME_CONFIG_MONGODE_SERVER-mongodb \
mongo-express
im facing
docker: invalid reference format: repository name must be lowercase.
Please help as i double checked capitl letters.
i tried other stack flow answers but still facing this error.
Related
I tried to create a mongo-express container using the command below:
docker run -d \
-p 8081:8081 \
-e ME_CONFIG_MONGODB_ADMINUSERNAME =mongoadmin \
-e ME_CONFIG_MONGODB_ADMINPASSWORD =secret \
--net mongo-network \
--name mongo-express \
-e ME_CONFIG_MONGODB_SERVER =mongodb \
mongo-express
And got the error:
docker: invalid reference format.
This question already has answers here:
Why docker container exits immediately
(16 answers)
Closed 9 months ago.
I am new to this. I have installed docker on my Raspi. I am trying to install transmission on the docker. I use the following;
docker run --cap-add=NET_ADMIN -d \
--name=transmission \
-v /mnt/extDrive1:/data \
-v /etc/localtime:/etc/localtime:ro \
-e CREATE_TUN_DEVICE=true \
-e OPENVPN_PROVIDER=EXPRESSVPN \
-e OPENVPN_CONFIG=my_expressvpn_uk_-_london_udp \
-e OPENVPN_USERNAME=XXX\
-e OPENVPN_PASSWORD=XXX \
-e WEBPROXY_ENABLED=false \
-e LOCAL_NETWORK=192.168.0.0 \
--log-driver json-file \
--log-opt max-size=10m \
-p 9091:9091 \
haugene/transmission-openvpn
I go through the debug on https://haugene.github.io/docker-transmission-openvpn/debug/
All is fine until I get to the section 'Checking if Transmission is running'.
When I run docker ps, there are no containers in the list.
What have I done wrong? Ultimately, I am trying to access transmission through localhost:9091.
Edit: So I have made some progress, but still having issues;
docker start transmission temporarily. populates the container ID
docker exec -it <container-id> bash comes up with the following error:
Error response from daemon: Container XXXX is not running
It seems that container is exiting out as you are not running it in the detached mode. Try this:
docker run -itd --cap-add=NET_ADMIN -d \
--name=transmission \
-v /mnt/extDrive1:/data \
-v /etc/localtime:/etc/localtime:ro \
-e CREATE_TUN_DEVICE=true \
-e OPENVPN_PROVIDER=EXPRESSVPN \
-e OPENVPN_CONFIG=my_expressvpn_uk_-_london_udp \
-e OPENVPN_USERNAME=XXX\
-e OPENVPN_PASSWORD=XXX \
-e WEBPROXY_ENABLED=false \
-e LOCAL_NETWORK=192.168.0.0 \
--log-driver json-file \
--log-opt max-size=10m \
-p 9091:9091 \
haugene/transmission-openvpn
My goal is simple: Load a hello-world external plugin for Kong. I've decided to do this via mounted volume, but am running into significant problems that stop me from being able to run my simple hello-world external plugin.
I've isolated my problem down to the following commands, from scratch:
docker network create kong-net
docker run -d --name kong-database \
--network=kong-net \
-p 5432:5432 \
-e "POSTGRES_USER=kong" \
-e "POSTGRES_DB=kong" \
-e "POSTGRES_PASSWORD=kong" \
postgres:9.6
docker run --rm \
--network=kong-net \
-e "KONG_DATABASE=postgres" \
-e "KONG_PG_HOST=kong-database" \
-e "KONG_PG_PASSWORD=kong" \
-e "KONG_CASSANDRA_CONTACT_POINTS=kong-database" \
kong:latest kong migrations bootstrap
docker run -it --name kong \
--network=kong-net \
-e "KONG_DATABASE=postgres" \
-e "KONG_PG_HOST=kong-database" \
-e "KONG_PG_PASSWORD=kong" \
-e "KONG_CASSANDRA_CONTACT_POINTS=kong-database" \
-e "KONG_LUA_PACKAGE_PATH=/plugins/?.lua" \
-e "KONG_CUSTOM_PLUGINS=helloworld" \
-e "KONG_PROXY_ACCESS_LOG=/dev/stdout" \
-e "KONG_ADMIN_ACCESS_LOG=/dev/stdout" \
-e "KONG_PROXY_ERROR_LOG=/dev/stderr" \
-e "KONG_ADMIN_ERROR_LOG=/dev/stderr" \
-e "KONG_ADMIN_LISTEN=0.0.0.0:8001, 0.0.0.0:8444 ssl" \
-v "kong/plugins/helloworld:/plugins" \
-p 8000:8000 \
-p 8443:8443 \
-p 8001:8001 \
-p 8444:8444 \
kong:latest
In my local directory, I have the plugin source code sitting in ./kong/plugins/helloworld/
According to the Kong docs, I'm adjusting my Kong config file by adding "KONG_" prior to the item I want adjusted. This means I have KONG_CUMSTOM_PLUGINS=helloworld and KONG_LUA_PACKAGE_PATH=/plugins/?.lua
Docker and Kong doesn't like this, and when running the above commands I am greeted with the following:
docker: invalid reference format.
See 'docker run --help'.
Eliminating things one-by-one, the problem surrounds both the -e "KONG_CUSTON_PLUGINS=helloworld" and -e "KONG_LUA_PACKAGE_PATH=/plugins/?.lua" \ bits.
What's going wrong here?
How can I run TimeScale on Docker on a ARM architecture with the Postgres/TimescaleDB data volumes exposed to the host?
My idea was to do the following:
docker run -d --restart always \
--name timescaledb \
-p 5432:5432 \
-e POSTGRES_PASSWORD=password \
-e POSTGRES_USER=user \
-e POSTGRES_DB=databasename \
-v /etc/postgresql:$PWD/postgres/etc \
-v /var/log/postgresql:$PWD/postgres/log \
-v /var/lib/postgresql:$PWD/postgres/lib \
timescale/timescaledb
However, TimescaleDB seems to be stuck in the start/ restart process:
Do you have any suggestions / ideas what I'm doing wrong?
Question is available on Github, too: https://github.com/timescale/timescaledb-docker/issues/23
The docker log (docker logs timescaledb) tells the following:
standard_init_linux.go:190: exec user process caused "exec format error"
Running
docker run \
--name timescaledb \
-p 5432:5432 \
-e POSTGRES_PASSWORD=password \
-e POSTGRES_USER=user \
-e POSTGRES_DB=databasename \
timescale/timescaledb
returns the same error: standard_init_linux.go:190: exec user process caused "exec format error"
I will check if the image supports ARM architectures. Follow up for more information is here: https://github.com/timescale/timescaledb-docker/issues/25
I’m trying to run kong on docker\kubernetes and I tried a bunch of images (0.13, 0.11, 0.11,2, some of the alpine images) and all of them share the same feature. if I run kong inside of those nothing happens. doing echo $? returns 132. i tried running /usr/local/bin/kong but the result is the same.
Is it just me or all of those are broken?
I’m using ubuntu 16.04\windows docker hosts with one of the latest docker versions. both of them fail in this same manner.
If they are fine, please explain what am I doing wrong?
I found the issue (no idea how to work around it at the moment though). The problem lies with the exit code 132: SIGILL – illegal instruction.
cat /proc/cpuinfo
model name : AMD Opteron(tm) Processor 4171 HE
This leads us here, which kind-of gives away the sad part: this processor doesn't support SSE 4.2. Here is the proof.
What you need to do to run Kong:
Set up a database, normally Cassandra or PostgreSQL e.g. like this:
docker run -d --name kong-database \
-p 5432:5432 \
-e "POSTGRES_USER=kong" \
-e "POSTGRES_DB=kong" \
postgres:9.5
You need to run kong migrations up in a shell inside of the container once:
docker run --rm \
--link kong-database:kong-database \
-e "KONG_DATABASE=postgres" \
-e "KONG_PG_HOST=kong-database" \
kong kong migrations up
Start with the matching environment:
docker run -d --name kong \
--link kong-database:kong-database \
-e "KONG_DATABASE= postgres" \
-e "KONG_PG_HOST=kong-database" \
-e "KONG_PROXY_ACCESS_LOG=/dev/stdout" \
-e "KONG_ADMIN_ACCESS_LOG=/dev/stdout" \
-e "KONG_PROXY_ERROR_LOG=/dev/stderr" \
-e "KONG_ADMIN_ERROR_LOG=/dev/stderr" \
-e "KONG_ADMIN_LISTEN=0.0.0.0:8001" \
-e "KONG_ADMIN_LISTEN_SSL=0.0.0.0:8444" \
-p 8000:8000 \
-p 8443:8443 \
-p 8001:8001 \
-p 8444:8444 \
kong
If you leave out the second step, kong won't start saying it needs the migrations to run.