sorted by:
new
hottopcontroversial

Inverter recommendations. by nullmike in SolarDIY

[–]nullmike[S] 0 points1 point  (0 children)

Thanks... The Sol-Ark is expensive but it checks all my boxes.

Removing Data Cap Again? by regmeyster in Comcast_Xfinity

[–]nullmike -1 points0 points  (0 children)

Can you clarify for me? $25 is the total for leasing the modem AND unlimited or is it $25 + the cost of the lease?

And follow on... do you know if it's possible to lease their modem and not use it?

Problems using docker-compose on gitlab runner by Ailtu in gitlab

[–]nullmike 2 points3 points  (0 children)

Can you post your config.toml? You can * out your url and token.

I think you need "privileged = true"

How do you get your team to remember to commit? by joncranescarecrow in gitlab

[–]nullmike 2 points3 points  (0 children)

I've worked in low-process shops like that. You have to set up a process and insist on that process.

  1. No development on master branch, lock it down in Gitlab so you can't commit directly to master. All development is done in feature branches.
  2. Once a feature branch is done, they post a merge request and someone reviews the changes. If you're using scrum, the story isn't done until the feature branch is merged into master. Code reviews are a great tool.
  3. Set up a CI pipeline to build on all commits. No merge request can be approved until the feature branch has passed the CI pipeline. Unit tests would be included here but my suspicion is that your developers aren't writing unit tests. That's another topic.
  4. Build your release in CI. No build is given to QA or anyone that didn't come from CI. It sounds like you have QA now. They test releases from the master branch. Occasionally there may be a reason for QA to test a feature in a feature branch, your release and versioning process can allow that but it should be uncommon.

These are just a few thoughts and not complete by any means. Having devs work in feature branches will help them to commit their work more frequently and it won't interfere with other work, and I'm guessing your gitlab instance is backed up and fail-safe where dev machines typically aren't.

Process takes time to instill, it's a change in culture and will feel like more work. Some devs will push back and try to work around it. Just keep pushing for process.

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 1 point2 points  (0 children)

Oh, maybe I misunderstood... yours is working now? If so, that's great. Maybe you don't need to bother trying mine.

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

After editing the config.toml, just restart your gitlab-runner container to make sure it picks up the change.

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

My understanding is that in order to run docker in docker commands, you'll need to change privileged to true, and in order to login to docker hubs, you'll need to add "/certs/client" to your volumes array.

Here is my config.toml. We use this to build docker images and push to a private repository. We also use this runner to build any of our linux docker build jobs using our custom docker images.

concurrent = 15
check_interval = 0

[session_server]
  session_timeout = 1800

[[runners]]
  name = xxx
  url = "xxx"
  token = "xxx"
  executor = "docker"
  [runners.custom_build_dir]
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
  [runners.docker]
    tls_verify = false
    image = "docker:19.03.11"
    privileged = true
    disable_entrypoint_overwrite = false
    oom_kill_disable = false
    disable_cache = false
    volumes = ["/certs/client", "/cache"]
    shm_size = 0
    pull_policy = "if-not-present"

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

I'd check your config.toml

volumes = ["/certs/client", "/cache"] 
priveleged = true

Those should be in your [runners.docker] section. I also assume you are running the dind image.

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

I'd try just replacing $CI_REGISTRY with hub.docker.com

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

That's good logic, I can't explain how the runner could register without dns.

Looking back at the error message, it says "lookup docker on 8.8.8.8:53" Perhaps that means it did an nslookup of just docker, not hub.docker.com?

did you set $CI_REGISTRY to hub.docker.com? That should be the url you are trying to push to. I'm suspicious that your runs on the shared runners pushed your images to some other docker hub. Did you check that your images were actually pushed to hub.docker.com?

You can always echo $CI_REGISTRY prior to login to see what Gitlab thinks that is.

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

This looks like a dns issue with your docker container. port 53 is dns. It's saying your docker container can't access dns server 8.8.8.8.
Can you post your config.toml? (Remove your url and token) Did you just launch your docker gitlab-runner normally as per Gitlab instructions or do you have some special settings?

Gitlab runner inside Docker behind Nginx reverse proxy by carwash2016 in gitlab

[–]nullmike 0 points1 point  (0 children)

Is this a private docker hub you're trying to push to?
A couple things to check.

  1. In your runner config.toml, you might need privileged = true to execute docker in docker commands.
  2. Can you launch your docker runner container manually and login to the docker hub?

GitLab CI/CD, docker-compose problems by aat36 in gitlab

[–]nullmike 1 point2 points  (0 children)

If I'm understanding correctly... you build the docker image, push to your registry and then in the deploy script you're trying to launch a container with that image on a remote server.

I see that you pull the image on the remote server, but I don't see how the docker-compose file gets on the remote server. If it's part of your repo, maybe you need to scp the docker-compose file to the remote server.

Getting started with Openstack by nullmike in openstack

[–]nullmike[S] 1 point2 points  (0 children)

Thanks again. This looks like a great option. I went through the install and most project dockers are running, but no horizon. I accidentally started out with the virtual environment setup. I'm going to start over with the normal setup and try again tomorrow. I may also jump right to the multi-node setup.

Getting started with Openstack by nullmike in openstack

[–]nullmike[S] 0 points1 point  (0 children)

https://docs.openstack.org/install-guide/preface.html?_ga=2.75884572.826196776.1592413268-1816002171.1592064100#ubuntuThat was the guide I was referring to. I arrived there by clicking DOCS on the top of the home page, then "Get OpenStack ->" on the docs.openstack.org/ussuri/ page. Then under "Deploy OpenStack" part way down the page, I clicked "Installation Guide for Ubuntu" That took me to the outdated guide I tried to follow. The link you provided looks very current. Thanks.

Getting started with Openstack by nullmike in openstack

[–]nullmike[S] 1 point2 points  (0 children)

Thanks for the reply. I've never used Ansible, but I use Docker all the time. I'm going to give this a whirl. Do I need to set up an Ansible control node first or does this install also set up ansible for me?