New answers tagged

0

I might have skipped the optional installation of docker in my Ubuntu instance, so if the gitlab runner is going to use Docker, remember to install it: curl -sSL https://get.docker.com/ | sh I got back to this issue and seem to have partially fixed it by checking it the gitlab runner is running gitlab-runner status systemctl is-enabled gitlab-runner ...


0

You'll want to look through the Kubernetes Volume documentation to see what options are available. In particular look into the PersistentVolumeClaim. This allows you to setup a shared data volume for your pods. Here's an example snippet from a k8s deployment YAML using a volume: spec: containers: - image: **yourdbcontainer** name: ...


0

simple dive.. docker ps check the current running images.. FROM ubuntu16 MAINTAINER sreeni (email/domain) RUN apt-get update RUN apt-get install -y nginx ENTRYPOINT [“/usr/sbin/nginx”,”-g”,”daemon off;”] EXPOSE 80 (port) simple docker file... docker run -d -p 80:80 --name webserver ubuntu16(imagename) after that check localhost or ip adress:80


0

After some more time I found my answer. The service I wanted to deploy was a slightly different version of a service we already have. Stack file for the "original" service: version: '3.7' services: my-service: image: my-repo:port/company/my-service ports: - 81:81 networks: - my-network deploy: replicas: 1 restart_policy: ...


0

Actually you need to implement per feature branch deployment. Because development environment use for testing app before QA. And feature branch deployment is very difficult to implement especialy at the begginging of devops. May be at start will be enough to use docker-compose to build latest version of developer's application. On their localhost.


1

SOLUTION APPROACH The approach is to create a macvlan. This will create a virtual adapter, that is allowed to lease an IP address from the subnet defined. 1) Activate Promiscous Mode For the virtual adapter one must enable promiscuous mode in the network. For Unifi controllers, do a SSH to your gateway and set: ifconfig [interface] promisc Some network ...


1

When you ping nginx the docker swarm returns Virual IP of swarm service named "nginx" not the container ip. This is is how internal load balancer works - you can have multiple replicas of "nginx" containers behind the "nginx" service.


1

There are some fundamental misunderstandings in your bullets which makes your question unclear: Apple will not allow you to develop/build using a virtual system. I believe this is a legal constraint. That said, you can run pretty much anything in VirtualBox as long as you have a legally provided image (e.g. a Linux image). You can only run the Windows ...


2

docker image inspect - will show available information on the container (docs) docker image history [your OPTIONS] imagename - Shows history of the container (docs)


0

There is stages in gitlab ci and on 'docker build' stage I don't need ALL env variables. Usually its only a REACT_APP_SERVER_URI variable. Later I use env file in compose.yml like you are. env_file: - ./envs/common.env


0

I want to avoid situtations where someone with access to the machine can just copy out some user data, or even look at it. You cannot stop someone with local access to the machine from reading data on the machine. Full stop.


2

Welcome to DevOps SE! A dry run for docker-compose seems to be an open feature request.


0

(Kublr CTO) If you can use Kubernetes as the deployment target for your applications, it is a great tool to standardize delivery and operations. The only problem is, as you correctly pointed, a consistent approach to deployment and operations of Kubernetes clusters themselves. The best practice in my opinion is definitely to centralize and unify Kubernetes ...


0

A side-note (sorry, I haven't got enough reputation to post direct comments yet): I see you are basing your image off of Ubuntu (FROM ubuntu:bionic) and then installing Apache... I would suggest using an image that's already tailored for this function, such as the Apache HTTP Server.


0

Review the containers' output in your terminal. If it was run in detached mode (with -d flag) then the you can review its output using docker container logs <container name>. If the container doesn't behave as planned but also doesn't exit, you may want to diagnose parts of your application from inside the container. You can do this by creating an ...


0

As per the error, it looks like the resolution is not happening for host xxxxx-xxxxx-xxxx.xxxxxxxxx.us-east-2.rds.amazonaws.com'. I mean the hostname is not getting resolved to the IP address from inside the container. You may need to check if the DNS resolver is working properly from inside the container or not. For testing, you can try to use the IP ...


1

If you can keep one common deployment strategy across both that would be simpler and less effort from the ops side of things. Kubernetes seems to be a great choice for the cloud orchestration layer at this point in time. Does Kubernetes make sense for the on-prem side though? If you're not planning on each on-prem install including 5-10 servers to spread ...


1

Check https://github.com/helm/helm/issues/3130, this might help. I followed the instruction in the post: kubectl --namespace kube-system create serviceaccount tiller kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller helm init --service-account tiller --upgrade This works for me.


1

Check out the dockerd options. This will apply to all containers managed by the Docker Daemon. Docker also has quite a bit of documentation on how to enforce different standards and compliance here.


2

The first thing you'll want to do is look for errors. It sounds like you have a Dockerfile that is creating an image, but when you run the image it appears to not do anything. There are two immediate things you can do to troubleshoot this: Do not use the -d flag when running the image. This flag runs the container in detached mode and will not display ...


1

I ended up using {{.ManagerStatus.Addr}} and stripping the port number from the results with sed. for NODE in $(docker node ls -f 'role=manager' --format '{{.Hostname}}'); do docker node inspect --format '{{.ManagerStatus.Addr}}' ${NODE} | sed 's/:2377//' done


1

First of all, I would not recommend to use a single system for running stable and testing version both on the same system. There are many reasons for this such as: Your testing version can cause cpu and memory spikes on system which will ultimately affect your stable version and end users. Secondly, it will be difficult to manage the dependencies and ...


Top 50 recent answers are included